[geos-devel] CAPI and libtool (question for BSD users)
strk at refractions.net
strk at refractions.net
Thu Feb 9 12:45:27 EST 2006
On Thu, Feb 09, 2006 at 05:41:46PM +0100, Eric Faurot wrote:
> On 2/9/06, strk at refractions.net <strk at refractions.net> wrote:
> > The CAPI has a new function GEOSArea().
> > Libtool manual says that this should trigger
> > an INTERFACE_CURRENT increment, so from
> >
> > CURRENT=1
> > AGE=0
> > REVISION=1
> >
> > we should go to
> >
> > CURRENT=2
> > AGE=1 // support all previous interfaces
> > REVISION=0
> >
> > I know this will bring to libgeos_c.so.1.1.0
> > under GNU/Linux, but IIRC on BSD systems this
> > resulted in 2.0.0 instead, if not worst.
> >
> > Is there any BSD user willing to test this ?
> > Basically we need to check:
> >
> > 1) what would the resulting library
> > SONAME be in BSD
> >
> > 2) if 2.0.0 wheter ABI compatibility
> > is really broke or not (could
> > be libtool is right)
>
> As far as OpenBSD is concerned, version info <current>:<revision>:<age>
> results in lib<name>.so.<current>.<revision>, ignoring age completely.
But. Why ?!
Is it a libtool bug or is there a reason ?
--strk;
> That said, the package team decided to takeover library versioning in
> ports. So anyway I do not think it is really necessary for you to try
> to come up with a portable scheme wrt versioning, as it will eventually
> be controlled by the packagers. They just need to be informed of backward
> compatibility issues between releases to know if a major bump is required
> or not.
>
> Eric.
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel
--
+----------------------------------------+
| Fight against software patents in EU! |
| www.ffii.org www.nosoftwarepatents.org |
+----------------------------------------+
More information about the geos-devel
mailing list