[pkg-crosswire-devel] RFS: sword, sword-text-web

Roberto C. Sánchez roberto at debian.org
Wed Nov 11 16:25:52 GMT 2020


On Wed, Nov 11, 2020 at 05:18:28PM +0100, Teus Benschop wrote:
> On Wed, 11 Nov 2020 at 17:03, Bastian Germann <bastiangermann at fishpost.de>
> wrote:
> 
> > Am 11.11.20 um 16:54 schrieb Teus Benschop:
> > > Hi Bastian,
> > >
> > > In the new sword package, the library is called "libsword1.9.0". The
> > > existing library is called "libsword-1.8.1". The difference between these
> > > two, apart from the version number bump, is the omission of the hyphen in
> > > libsword 1.9.0. Instead of libsword-1.9.0 it is called libsword1.9.0.
> > >
> > > Is that version number without the hyphen what you prefer?
> > >
> > > General question: Is the notation "libxxxversion" acceptable instead of
> > > "libxxx-version"? Or what is in general use?
> >
> > In general, the lib pkg should be named after the SO name. Upstreams
> > should care about their SO names, which Sword does not seem to do. If
> > you build via autotools you will get an SO name with a hyphen and with
> > cmake you will not get one. That is why the changed was introduced with
> > the switch to cmake.
> >
> > In my opinion, it would be preferrable if the upstream soname changed
> > only when necessary, i.e., with ABI breaking changes and not with every
> > release.
> >
> 
> 
> Ah, okay, it's clear why there's no hyphen, I think the reason for that is
> clear, I am fine with that.

Still, it would be nice if upstream library authors would take the time
to learn how things like ABI and binary compatibility work and then
manage appropriately.  Sadly, this problem (no proper ABI management) is
somewhat common.

Regards,

-Roberto

-- 
Roberto C. Sánchez



More information about the pkg-crosswire-devel mailing list