Hi, Yavor Doganov wrote: > > I'm afraid I don't understand the question. If upstream bumps the > SONAME, it isn't distro-specific in anyway, right? AFAICT, (in Debian > at least; I'm not aware of other practices) a distro-specific SONAME > for a library is introduced when > > 1) An ABI breaking Debian-specific patch has been added; which > - might be rejected by upstream (for whatever reason); > - might be a bugfix already present upstream, but > ABI-incompatible with the version in Debian (as is the case). > 2) A new upstream release is ABI incompatible, but upstream forgot > to indicate that with the proper mechanism (this happens quite > often for ObjC libraries, unfortunately). > 3) Upstream is providing a library, but it doesn't have any > interface versioning mechanism (as some of the Mozilla > libraries). > 4) Something else I surely forget.
Thanks for the clarification, i am pretty lost here. > > So, you should make sure that upstream bumps the SONAME for next > release (0.13?), because there are ABI breaks all over the place > (affecting all public libraries). For the current transition, the > attached minimized patch seems to work for me, Ok, thanks a lot, it have worked in my tests too. > but don't forget to: > > - Perform extensive runtime tests; most changes are not trivial. > - Rename the runtime library to libgnustep-dl-0d (debian/control); > and update dependencies (this implies passing through NEW). > - Amend debian/rules to cater for the package rename. > - Rename debian/libgnustep-dl-0.install as > debian/libgnustep-dl-0d.install and adjust the EOControl entry for > soname change. > I've uploaded to mentors a new version with all these changes applied, could you please take a look [1]? [1] http://mentors.debian.net/debian/pool/main/g/gnustep-dl2/gnustep-dl2_0.12.0-4.dsc Cheers, Federico
signature.asc
Description: OpenPGP digital signature
