Pristine source archive

Glenn McGrath bug1 at optushome.com.au
Sat Apr 13 07:24:16 UTC 2002


The free software community is wasting resources due to the fragmented
approach to the format of source code distribution.

The source packages of all distributions are based on the same upstream
source code, however distributions combine their metadata and patches in
different, possibly incompatable ways.

The problem with this aproach.
 - Storage space: Mirrors contain the source code packaged in different
ways for every distribution they mirror - Availability: If a user wants
the pure source code to an application its easiest if they go via the
projects home page, distributions _may_ have modified the source code, or
the latest version may not be available yet.

I would like to see a co-operative distribution method between
distributions and the individual project release managers that - Allows
upstream project managers to optionally sign, or in other ways
authenticate the source in the archive is unmodified. - Allows
distributions to use the pristine source archive as the primary source of
their upstream source code, leaving only the metadata and patches in their
source package.

I believe this aproach would
 - make distributions more accountable to their users as its easier to see
how a project's source code has been modified by the distribution. -
Reduce the space requirements for mirroring free software, possibly
leading to greater availability of source code. - Make it easier for
smaller unrecognised distributions as they can draw from the common pure
source archive. - Encourage greater co-operation between distributions...
maybe even one day leading to a common metadata format.

I imagine the biggest problem with this idea is getting distributions to
use it, which would probably require modification of their archive and
package managment tools.

Distributions who use it would have to be able to upload to the master
archive if the source package wasnt already there, and not be allow to
remove a package unless its not used by anyone... which may be a problem
determining.

I mentioned it here as i think such an effort would have to be independent
of any one distribution.

What do you all think, is it a good/bad idea, would it have ant chance of
being acceptanced ?



Glenn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://spi-inc.org/pipermail/spi-general/attachments/20020413/6a2b9c58/attachment.pgp


More information about the Spi-general mailing list