Re: RFC: APR 2.0 modularization

On Mon, 22 Apr 2024 at 17:01, Joe Orton <[email protected]> wrote:

> On Sat, Apr 20, 2024 at 12:38:20PM +0200, Ivan Zhakov wrote:
> > 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.
>

[...]


> Open
> questions on where to draw the line, as to what goes in a separate
> library, and much more I'm sure.
>
Well, it's a good question. I was thinking about something like that:
"everything that can be used in libapr-*-2 should be in libapr-[core]-2".
I mean in **general** we should avoid dependency like app -> libapr-ABC ->
libapr-XYZ -> libapr. Another way to draw the line is to move *everything*
that incurs external dependency to a separate library.

-- 
Ivan Zhakov