[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Allow to build with full path to neon-config.

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 14 Dec 2009 17:56:50 +0000

Alexander Thomas <alexander_at_collab.net> writes:

> On Mon, 2009-12-14 at 13:47 +0000, Philip Martin wrote:
>> Alexander Thomas <alexander_at_collab.net> writes:
>>
>> > [[[
>> > Allow build against the full path to neon-config.
>> >
>> > * build/ac-macros/neon.m4
>> > (SVN_LIB_NEON): Modified to accept full path to neon-config. Fixed doc
>> > string accordingly.
>> > ]]]
>>
>> What's the rationale for this change? Does it fix something?
>>
> This don't fix anything. I'm only trying to make --with-neon option
> consistent with other options like --with-apr/apu, which already
> supports a full path to respective *-config files. So why not we do the
> same with neon ?

The apr[-util] location stuff is copied from those projects. The
Subversion stuff tends to behave like --with-neon, look at --with-swig
and --with-gssapi. It doesn't seem like an important thing to change,
and like any build change it risks breaking obscure platforms. You
are using "test -x" and I see that find_apr.m4 explicitly avoids that
on OS/2.

-- 
Philip
Received on 2009-12-14 18:57:22 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.