[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [issues] Why eglibc does not provide tarball?

On Fri, May 15, 2009 at 8:43 AM, Gaye Abdoulaye Walsimou
<walsimou@xxxxxxxxxxxx> wrote:
> This is not really an issue, but it would be useful to have tarball
> and/or svn tags for each eglibc release.
> Why such things do not exist?

Gaye's email anticipates one that I was about to send to this list, so
I'll send this as a reply to it.

I prefer to get released versions of projects in the form of tarballs,
preferably signed ones. I'm sure I'm not alone in that preference:
tarballs can be signed, so as to provide an assurance that they have
not been tampered with or accidentally corrupted, and tarballs are
much easier to mirror at archive sites all over the Internet than
source repositories are. Also, in many cases, downstream projects that
make use of a project like eglibc -- say, Linux distributions or build
notes -- assume that the code for each of their dependencies can be
found at an http or ftp URL, which doesn't work well if the only
upstream source is a source repository.

All of this being the case, I think it would be worthwhile if eglibc
releases were available in that form. Are there any current plans to
create such tarballs?

If not -- I've already created tarballs based on all of the eglibc
release branchpoints, along with patches that can be used to get to
the current version for each release. (I'm also willing to commit to
preparing further release archives and patches indefinitely, as a
minor contribution to the eglibc project.)

Currently these are hosted at
http://toolchain.freesa.org/eglibc-tarballs/ but I think it would be
much better if release tarballs were hosted on some eglibc.org site.
Does that seem feasible? If the maintainers of the eglibc.org site
don't have space or bandwidth available to host release tarballs, or
aren't inclined to do so, perhaps a DNS entry "releases.eglibc.org"
could be created that points to the current server...


Brett Neumeier

Brett Neumeier (bneumeier@xxxxxxxxx)