apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Erenkrantz <jus...@erenkrantz.com>
Subject Re: [PATCH] update find_ap{ru}.m4 for ap{ru}-1-config was Re: 1.0.0 RC4 (apr-config -> apr-1-config)
Date Thu, 15 Jul 2004 18:00:34 GMT
--On Thursday, July 15, 2004 9:07 AM -0700 Noah Misch <noah@cs.caltech.edu> 
wrote:

> If APR_FIND_APR accepts version constraints, should it not interpret them
> to at least the maximum granularity at which APR allows API changes?  I
> think this is not difficult:

I disagree.  When you have multiple parallel installs of the same major 
version all sorts of things can go wonky.

In your scenario, imagine: /usr having apr-1.1.5 installed and then 
/opt/apache having apr-1.2.5 installed.  That's going to be a nasty 
conflict when the user tries to run it depending upon the characteristics 
of the run-time linker (not to mention compiler search order).  You might 
override the one in /usr/lib with the one in /opt/apache or you might not.. 


I'd strongly prefer we not open the door to a slew of errors.  The 
granularity should be at the major version and no finer.  -- justin

Mime
View raw message