Re: Squid sub-libs

Alex Rousskov wrote:
> On Sat, 2008-03-08 at 10:52 +1300, Amos Jeffries wrote:
>> In line with the 3.1 cleanup and re-arranging I'd like to propose a
>> change to the naming scheme of the *.la files squid produces.
>>
>> Namely that they get called libsquid-X.la instead of just libX.la.
>>
>> This would mean:
>> libsquid-auth.la, libsquid-fs.la, libsquid-icap.la, libsquid-esi.la,
>> libsquid-acl.la, etc
>>
>> That will reduce some makefile confusion between external libraries and
>> ones built into squid. Case in point: we already have two libmisc.* linked.
>>
>> Input?
>
> I think we should link with group/libgroup.la libraries and compile with
> group/name.h headers rather than adding Squid prefixes everywhere. If we
> want Squid prefix as an extra protection, we could use
> squid/group/name.*
>

What happens then after you decide to publish the group headers for eCAP?
People linking against libgroup.l.so as they need? or one monolithic
libsquid.l.so with all squid headers needed by the smallest client app?

Amos

-- 
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.