[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [issues] Why eglibc does not provide tarball?
- To: Brett Neumeier <bneumeier@xxxxxxxxx>
- Subject: Re: [issues] Why eglibc does not provide tarball?
- From: "Joseph S. Myers" <joseph@xxxxxxxxxxxxxxxx>
- Date: Sat, 16 May 2009 19:10:32 +0000 (UTC)
On Sat, 16 May 2009, Brett Neumeier wrote:
> like to do this under the auspices of the eglibc project per se, so
> that people who want to get eglibc releases in the form of tarballs
> can do so by going to eglibc.org...does that seem feasible? Feel free
There is no such thing as an EGLIBC release; a tarball claiming to be such
would be masquerading as something that does not exist. It would be up to
the EGLIBC Consortium if they wish the project to start providing releases
or snapshots as tarballs (but if they do then it would make no sense to
take them from third parties; building a tarball is easier than verifying
one). As with the lack of releases, there is no release number scheme for
identifying points on branches other than SVN revision numbers; the only
meaningful naming system would be to name snapshots (created by svn export
of the branch directory - not the libc/ports/localedef subdirectories -
followed by touching checked-in generated files to get timestamps in the
right order) after the branch version and the SVN revision number of the
most recent revision on the branch at the point the snapshot is created,
e.g. 2.10-8454. (The branchpoints are definitely bad points to use; only
tip of a branch might be sensible for creating snapshots.)
--
Joseph S. Myers
joseph@xxxxxxxxxxxxxxxx