On Tue, Sep 1, 2009 at 8:03 PM, Mike Frysinger<vapier@xxxxxxxxxx> wrote: > i think the question was one about packaging rather than general use ? if you > build a package against a newer glibc version but it only uses older symbols, > then in theory it should work fine with older glibc versions. if the symbol > changes between versions, then it should have corresponding symbol version > changes as well (which will automatically be recorded in the binary). Yes, the question is specifically about packaging. If the answer is "Debian does not prevent you from downgrading glibc, even if you have new packages built against the new glibc", then I accept that. However, I have another question. What prevents applications built on a buildd against a newer glibc, from being installed on a system with an older glibc? Glibc provides backwards compatibility, but *not* forwards. What happens in the packaging subsystem to prevent this? How does an application encode "I was built against glibc X.Y, therefore I should only be run on such a glibc or newer." Cheers, Carlos. -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
