The point is that, if we build against 1.1.2 (the way we used to build against 1.7.1 of SWORD, etc) then we are forced to execute a rebuild of the Xiphos and all other downstream packages just because the filename changes to 1.1.3 later on. Even though 1.1.2 and 1.1.3 are API/ABI compatible. By explicitly setting the SOVERSION to the earliest ABI-compatible version, or to a unique value that tracks ABI compatibility, we negate the need to force a rebuild of Xiphos every time we update biblesync.
--Greg On Mon, Aug 17, 2015 at 3:46 PM, Matěj Cepl <mc...@cepl.eu> wrote: > On 2015-08-17, 19:10 GMT, Karl Kleinpaste wrote: >> I pulled down the official (i.e. Greg's) BibleSync packages from Fedora >> repos to look inside them. His packages contain .so.1.1, not >> .so.1.1.2. Perhaps Greg did the soversion thing? But in the name of >> consistency, then, a Xiphos built against that BibleSync package should >> link fine using just .so.1.1. > > Package biblesync-1.1.2-3.el7 (from > https://kojipkgs.fedoraproject.org//packages/biblesync/1.1.2/3.el7/x86_64/biblesync-1.1.2-3.el7.x86_64.rpm > ) contains actually code of 1.1.2 but with the fake SOVERSION > set to 1.1. I really don’t get what’t the point. > > Matěj > > -- > http://www.ceplovi.cz/matej/, Jabber: mc...@ceplovi.cz > GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC > > If you are not paying for it, you're not the customer; you're the > product being sold. > -- blue_beetle (2010-08-26) > http://www.metafilter.com/95152/Userdriven-discontent#3256046 > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page