Previously Julian Gilbey wrote: > [I think that some version of the original message should be posted at > some point to -devel-announce, probably once the new dpkg-shlibdeps is > installed in woody. We also might need some NMUs if this occurs > during the potato freeze and many developers are working on frozen > rather than unstable machines.] I'll post a full explanation there once this is accepted and the new dpkg is about to be uploaded. This will definitely not be done in potato, I've been postponing this on purpose for that reason. > Obvious solution: the shlibs file in any library package (say libbar > in this example) must declare a dependency: libbar (>=version number) > where the version number must be *at least the first version which was > packaged using the new dpkg-shlibdeps*. Then when foo is compiled > against libbar in woody, it will depend upon the woody libbar, and > thus bring into play all of the sub-dependencies. Sounds like the proper upgrade procedure. I didn't put this in the proposal since it shouldn't be part of the policy itself but of an accompanying transition process. Wichert. -- ________________________________________________________________ / Generally uninteresting signature - ignore at your convenience \ | wichert@liacs.nl http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Attachment:
pgprjlV6GtJ2O.pgp
Description: PGP signature