On Sat, May 29, 2010 at 7:39 PM, Sander Temme <[email protected]> wrote:
> Wouldn't we rather move to a construct where APR is not needed to buildconf?  
> If all we're doing is copy in find_apr.m4, can't we just fork that and allow 
> it to evolve into our own idea of finding an appropriate APR against which to 
> configure?
>
> That would render the issue of buildconf against 2.x/trunk vs. configure 
> against 1.x moot.

The reason we added find_ap{ru}.m4 initially was to prevent exactly this fork.

For example, Subversion shouldn't have to re-create this logic either.
 So, I'd rather keep find_apr.m4 in apr - especially given all of the
other source dependencies in buildconf.  My itch-scratching doesn't
move me to want to replace buildconf at this time.  -- justin

Reply via email to