>When 1.1 is released, this bug can be closed, although I am not sure >how to handle the migration, since 1.1 is API and ABI incompatible.
The general rule is: change the package names (for the API change), and the library major soname version (for the ABI change). Version the symbols so both can be linked into the same program. That's 'best practice'. If upstream hasn't versioned their symbols, make the new packages Conflict: with the old ones. If upstream also hasn't changed their soname version, you may be able to get away with it by having Conflicts: against the old version and the old versions of any reverse dependencies (particularly if there aren't any, as in this case), but you probably shouldn't. Since libs11n0 has no reverse build-dependencies in Debian, you can get away with retaining the same -dev package name as well (you'll be breaking third-party builds which assume the old API, but oh well -- it's not absolutely required that -dev packages maintain the same API). You have to change the lib package name and make it Conflict: with the old library package anyway for the C++ transition. If upstream had the sense to change their soname, you will probably be able to just do that and upload the new version, with no other changes (and without even an ugly 'c2'). -- Nathanael Nerode <[EMAIL PROTECTED]> Make sure your vote will count. http://www.verifiedvoting.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
