Re: [Savannah-hackers] Re: commonc++ integrated to http://savannah.gnu.org/projects/commonc++/

[Loic Dachary]

David Sugar writes:

 > binary "packaging" formats, and in that normally there is only one
 > tarball to deal with per package for any given release, much of the
 > complexity in "later" versions of the SourceForge "package
 > distribution" forms can probably go away entirely.

 I came to the same conclusion.

 > Based on my own experiance with SourceForge, what I would love to
 > see for software distribution is a simple index page that showed
 > what tarballs are currently in the ftp directory for a given
 > package with some additional options and buttons on the page for
 > the package maintainers to use.  I would also love a mechanically
 > simpler one page form and single step submit to generate and
 > distribute a new package tarball release.  Finally, it would be
 > useful to allow a package maintainer to selectivily designate prior
 > releases for "archiving", to be able to revoke an active release if
 > nessisary, etc.

 I think the temporary upload directory is necessary to prevent
broadcasting incomplete tarbals to the mirrors. As far as archiving
goes, the policy of ftp.gnu.org changed recently and now recommend to
store all versions instead of archiving them. Anyway it will be needed
to offer the ability to remove/rename tarbals, in other words it's
needed to give a write access to the ftp directory for each package
maintainer. Wether is should be web based or rsync/scp based is not
decided at present. I tend to think that rsync would be much more 
convenient that anything we can imagine with a web interface.

 Cheers,

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
24 av Secretan         http://www.senga.org/      address@hidden
75019    Paris         Tel: 33 1 42 45 09 16        address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt