Re: Why are new package versions depending on libc6 in unstable?
On Mon, Nov 18, 2002 at 08:33:57PM -0500, Joey Hess wrote:
> Mike Fedyk wrote:
> > Is this part of the Debian policy (sorry, I haven't read it)? If it is
> > maybe that should be changed, or maybe it's there because of something I
> > haven't realized. If so, please let me know what it is.
>
> glibc provides backwards compatability, but not forwards compatability.
Ok, so compile/depend on the libc in testing...
> That is, a program built with an earlier version of libc6 will continue
> to work with later versions of libc6.
Exactly...
> But, a program built for a recent
> version of libc6 may not work with earlier versions. For example, it
> might end up built to use a version of a symbol that is not in earlier
> versions of libc6.
That doesn't explain why packages are depending on the newer libc6 in sid and
making them testing/sarge incompatible.
Thanks,
Mike
Reply to: