glibc 2.1 and compatibility (Was: slink is gone, goals for potato?
On Tuesday 2 March 1999, at 0 h 45, the keyboard of Edward Betts
> glibc 2.1 - lots of recompiles
As far as I know (can a real guru confirm/deny?), there is no binary compatibility between glibc 2.0 and 2.1 (like it was between libc5 and glibc). So we'll have a difficult move, like between bo and hamm. And the packages which are compiled on potat will not run on slink or hamm.
This is a serious problem for Debian :
- it means that real users, who do not run 'apt-get dist-upgrade' every morning, will have the feeling to be abandoned (the bugs will be fixed only on potato and you will have to upgrade to get the bug fixes. Worse, the BTS has no provision for a bug fixed only in unstable, this is a real pain for stable releases users).
- it means that new packages (most of my biology packages were made after the slink freeze a long time ago) will not be available unless you install potato (which is far from stable).
In practice, it means more work for the developers who want to serve all (keep two development environments and recompile for slink and potato each time they change something).
Will we have at least a libc6-dev which can coexist with libc6.1-dev so I don't have to run two machines to make my packages?