This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Update on freeze status of glibc 2.18?
- From: Russ Allbery <rra at stanford dot edu>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 20 Jun 2013 17:54:59 -0700
- Subject: Re: Update on freeze status of glibc 2.18?
- References: <20130617193649 dot 7B5872C08D at topped-with-meat dot com> <1371503900 dot 16968 dot 21902 dot camel at triegel dot csb> <20130619224234 dot 5AC132C10E at topped-with-meat dot com> <1371733830 dot 964 dot 1089 dot camel at triegel dot csb> <20130620140934 dot GZ6123 at two dot firstfloor dot org> <1371743530 dot 964 dot 1602 dot camel at triegel dot csb> <20130620205512 dot GD6123 at two dot firstfloor dot org> <1371765683 dot 964 dot 2885 dot camel at triegel dot csb> <20130620222454 dot GE6123 at two dot firstfloor dot org> <1371770055 dot 964 dot 3114 dot camel at triegel dot csb> <20130621001607 dot GF6123 at two dot firstfloor dot org>
Andi Kleen <andi@firstfloor.org> writes:
> On Fri, Jun 21, 2013 at 01:14:15AM +0200, Torvald Riegel wrote:
>> If you were talking about potential users, then which scenarios do you
>> have in mind? If people use the stock glibc that their distribution
>> provides, then the applications provided by the distribution will also
>> have been recompiled. That already gives you a large group of users
>> and applications, and good testing. If you're thinking third-party
>> binaries, then they'll have to be recompiled to make use of new
>> features -- but that's hardly unusual.
> AFAIK Fedora doesn't even recompile every release (I may be wrong).
Debian certainly doesn't. Most software in Debian ends up being
recompiled at some point during the release process simply because there's
usually some reason to upload a new version of the package, but if there
isn't, the same binaries may exist in multiple releases. There is no
proactive attempt to rebuild every binary in the distribution against the
latest glibc and upload the results. (We *do* rebuild every binary in the
distribution against the latest glibc *to make sure that it still builds*,
but the results are discarded unless there are build failures.)
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>