RFC: APR 2.0 modularization

Hi,

In APR 2.0 we merged APR-Util **project** to APR. Which is IMHO a good
thing.

But we also merged everything into one big library + modules for loadable
drivers, if APR_HAVE_MODULAR_DSO.

I think it's suboptimal:
1. Distributions have to decide what features to compile into this big APR
library.
2. Linking to APR-2 makes applications depend on multiple libraries, even
this particular application is not going to use them.

I would suggest separating APR in different libraries, while keeping them
in one project/source tree.

Something like that:
- apr-2
- apr-dbd-2
- apr-dbm-2
- apr-xlate-2 (?)
- apr-crypto-2
- apr-xml-2
- apr-ldap-2
- apr-memcache-2
- apr-redis-2

I want to clarify that I don't propose going back to apr-util time when APR
was splitted to separate projects: this proposal is only about libraries on
the disk.

What do you think?

-- 
Ivan Zhakov