Marcus Brinkmann <[EMAIL PROTECTED]> wrote: > > IMHO, the fundamental and unavoidable reason why we have this problem > is the following:
> We don't know in which Packages files (=distributions) a > single binary is (used or) going to be used. Perhaps I'm missing something, but I thought the whole point of having all these dependencies is so that as long as all of them are satisfied, that the package continues to work. If that's not the case, I think we better pack up and go home :) > This is a source for conflicts and inconsistencies, because whenever you > want to compile something you have to make sure it will be okay for all > distributions it is going to be used in. As this includes decisions made in > the future[1], there are potential problems you can't address. Well my position is that the people in future should make accomodations for you. This is what compatibility is all about. If a library changes its ABI, then it must change its soname (or at least their package name) so it doesn't break old binaries. Other things should also act accordingly. -- Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
