Re: glibc 2.2

[Andreas Jaeger]

On Tue, Dec 26, 2000 at 02:54:47AM +0000, Ali Akcaagac wrote:
> hello!
> 
> my name is ali akcaagac. please excuse my bad english unfortunately
> english is not my native language but i hope that i might be
> understandfull to you ;). i am running unix/linux for many years
> now. the past 1 year, i run a selfmade linux system at home, that
> i was hosting like someone else is hosting his car or however.
> 
> now that i don't use any distributions like redhat, suse, debian
> or whatever, i switched to glibc 2.2 a few weeks ago, this caused
> some problems after compiling and installing. sure there is maintainance
> missing, as it happen within professional distributions. be sure, i read
> everything i was able reaching within the glibc 2.2 tar archive.
> 
> now that i have these bugs for some weeks, i went to some irc channels
> and talked with some other unix/linux dudes online there. they told me
> that package maintainers like redhat, where mr. ulrich drepper works for
> (i dont know if this mail will reach drepper himself so i leave this)
> use to have many of these bugs fixed. (at least its no matter what kinda
> bugs fact is that they are fixed). i use to search for patches or
> whatever
> on ftp.gnu.org or alpha.gnu.org (?) unfortunately there is nothing.
> 
> i know it might be hard for you guys to keep track of all news and
> informations, but "glibc" and "gcc" are the heart of nearly every
> unix/linux system, and such patches, can't be left as an secret.
> i now downloaded the source rpm from redhat and will have a look at
> it soon, to figure out what changed. but i think these patches should
> really be offered here on gnu.org. because gnu.org and freshmeat are
> the first places i look for that and not e.g. redhat. it is really
> important to have them here..
> 
Ali,

the glibc and gcc developers use a CVS repository for the projects.  That
way you can access all patches directly.  For information about the
CVS access check http://sources.redhat.com/~glibc and http://gcc.gnu.org

There's no central set of patches for glibc 2.2 - and no secret
place.  Distribution makers and hacker can just grab those patches they 
need from CVS.  The glibc team - similar to the GCC team - does not make a new
release for every bug fixed like Linus does for the kernel.
Releasing patches means always a lot of regression testing on all supported
platforms and therefore releases take their time.

> i would like to get an answer for this email.
Btw. gcc/glibc are projects worked on by volunteers - you don't have
any contract with any of us developers.  But we do try to answer all
mails.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj