Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
Errors-To: <wrowe@rowe-clan.net>
Message-ID: <438E4409.7070004@rowe-clan.net>
Date: Wed, 30 Nov 2005 18:30:01 -0600
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929)
MIME-Version: 1.0
To: APR Developer List <dev@apr.apache.org>
Subject: Re: apr 0.9 quirks and default --prefix value?
References: <438E3BED.9090401@rowe-clan.net>
In-Reply-To: <438E3BED.9090401@rowe-clan.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

William A. Rowe, Jr. wrote:
> I'm noticing 0.9 has no default --prefix.
> 
> I also note apr-util-0.9 doesn't find apr-config in the path 
> (/usr/local/bin
> in this case.)
> 
> Finally I wonder why we continue to require the path to a source apr image.

It seems silly to have to specify;

./buildconf --with-apr=../apr-1.1
./configure --prefix=/usr/local --with-apr=`which apr-1-config`

when ./buildconf; ./configure  should just do the right thing.
The same issues apply to 1.0, 1.1, 1.2, and also;

Do we want to fix things before 1.3.0 so that we begin emitting a message

$ make install
Error: Cowardly refusing to overwrite a newer, installed version of APR
        run  make FORCE=1 install  to overwrite the existing version.

$ make FORCE=1 install
[...]

to prevent folks from hurting themselves?  Obviously this won't be truly
effective until apr 2.0, but it's a start.

Bill