Ryan Phillips wrote:

I agree APR and APR-util should be combined into one, but I hate the notion
of chunking the library into multiple parts.  If a developer wants to
disable a feature, then a simple --without-xml or --without-dbm should
suffice.

This works if you have built the library from source, or have built the library for embedded use (as you have), but when apr is deployed as a generic system library on a generic system (a significant use case), then this doesn't work.

Thinking about this for a bit, I think splitting the build into libapr, libapr-ldap, libapr-xml, etc is the best way forward on this one.

Regards,
Graham
--

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to