Shared library versioning policy

[Simon Barner]

Hi,

I recently asked the boost-devel list to review my port of the boost
library, and on the whole everything seems to be okay.

There is one issue, though: Starting with Boost 1.31.0, I forced shared
library version numbers: so.1 for Boost 1.31.0, so.2 for the current
1.32.0 release.
I now learnt that starting with version 1.32.0, Boost has its own shared
library version policy: so.1.32.0

This raises the following questions:
 - Is this naming scheme compatible to [1]?
 - Shall I change the port to use Boost's versioning scheme?
   o This would have the advantage to provide a port that is more
     compatible to the official boost distribution.
   o The drawback is that the port with so.2 libraries is already in our
     CVS repository, which would mean that the shared library version
     numbers would decrease.

Thanks for your advise,
 Simon

[1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/policies-shlib.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050107/9d4c3c48/attachment.bin