symbol versioning of private libraries builds

[Brad Hards]

On Saturday, December 11, 2010 12:49:23 am Volker Lendecke 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.

Brad