Re: libpthread shared library version number

On Fri, 3 Nov 2006, Ruslan Ermilov wrote:

> On Thu, Nov 02, 2006 at 01:19:37PM -0800, Maxim Sobolev wrote:
>> Ruslan Ermilov wrote:
>>> On Thu, Nov 02, 2006 at 08:09:48AM -0600, Brooks Davis wrote:
>>> Hmm, bumping not versioned libraries *now* and not bumping them
>>> again at pre-release would work, but doing it without also bumping
>>> "to be versioned" libraries is IMO pointless.  And if we bump all
>>> of them now, we'll have to bump some of them again when versioning
>>> is turned on by default.
>>
>> No, we will not have to do it. Why would we? It's -CURRENT, so that
>> nobody really cares about backward/forward compatibility within that branch.
>>
> I'd very much like NOT to have to recompile all of my installed
> ports on my -CURRENT boxes the day we turn on symbol versioning,
> and that will require the shlib major bump of those libs that
> will provide symbol versioning.  If we do the bump now, we'll
> have to do it again later, and that's slightly against the rule
> that we only bump them once inside a branch.

No, we don't bump library versions more than once in
-current in the same release cycle.  Yes, sometimes
this requires that you have to rebuild all your ports.

And you can safely enable symbol versioning without bumping
library versions -- libraries and binaries built against
non-symbol-versioned libraries will run just fine on
the same libraries with symbol versioning.  The thing
that won't work is trying to use libraries/binaries
built against symbol versioned libraries on those
same libraries _without_ symbol versioning.

I hope you can follow what I am saying, because it sounds
confusing even to me ;-)

-- 
DE