On Fri, Sep 20, 2002 at 10:48:41PM -0600, David Eastcott wrote: > Since glibc needs to be compiled against a kernel, and as a result that > kernels header files needs to be used by other programs compiled/linked with > glibc, then if a newer kernel is being released does it not also follow that > the glibc package also be rebuilt against the new kernel and released at the > same time? > > Guess this would also mean that all other packages would also have to be > rebuilt ... and, > > This is begining to sound kinda like the chicken and the egg thing. > > Perhaps a better choice would be to isolate the kernel dependant parts of > glibc into a seperate package and release that when ever the kernel is > upgraded?
The kernel doesn't change interfaces very often. Only time something would have to be rebuilt for a kernel would be if the kernel changed an interface. Same reason why you don't have to rebuild apps unless the major changes on libraries they use. Even if glibc required a rebuild for a kernel that wouldn't necessarily require a rebuild of the apps that depend upon glibc because glibc's interface probably wouldn't change. -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org Never take no as an answer from someone who isn't authorized to say yes.
