symbol versioning of private libraries builds

[Volker Lendecke]

On Sat, Dec 11, 2010 at 10:24:06AM +1100, Brad Hards wrote:
> > On Fri, Dec 10, 2010 at 08:42:48AM -0500, simo wrote:
> > > > but we have no way to enforce that, and I suspect it will happen.
> > > 
> > > In this case the best option is to abort immediately at application
> > > startup.
> > > Anything else is begging for obscure errors or crashes later on an big
> > > headaches.
> > 
> > Indeed. I've gone through some pain to remove the talloc
> > dependency from libwbclient for exactly that reason.
> Would the cleanest way to always build the public libraries and never do a 
> private link? That is, if multiple libraries / applications might want to 
> build against a library, then never allow it to be bundled.

An additional goal was to eventually make libwbclient
thread-safe. We're not there yet, but at this moment, it
would not be possible with talloc.

Volker