Karl Fogel wrote:
> Neels Janosch Hofmeyr <neels_at_elego.de> writes:
>> I have tried to compile subversion on a FreeBSD without a system wide
>> neon installation. Thus, I found that it makes no sense to supply the
>> --with-neon option:
>> I'd like to file this as an issue... so, do I wait for a buddy now?
> I don't have time to look into this right now, but it seems like
> you've gathered a lot of details on the problem, so +1 on filing an
> issue if there isn't one already. (Please point back to this thread
> from the issue.)
Well, stsp and I found out the reason why --with-neon wasn't accepting
source trees, because it is supposed to accept an *installed* neon
location. To use neon sources, one does not use --with-neon, but put the
neon sources in the trunk's root directory.
The problem that remains is that this detail is not given in the online
help. While the comparable option --with-serf accepts a source
directory, --with-neon accepts only a built and installed neon. So,
someone who used --with-serf will be confused by --with-neon,
particularly since they are competing libraries for the same functionality.
Basically, the only thing that really needs to be changed is the online
help for the --with-neon option (as in configure --help). There would
still be inconsistency (the two mentioned options work entirely
differently, although they look similar), but I guess that's just the
way it is, then.
Still, thanks for the plus-one! Do I still file an issue to change the
help information, or do I just send a patch?
Neels Janosch Hofmeyr
Public Key at
elego Software Solutions GmbH http://www.elegosoft.com
Gustav-Meyer-Allee 25, Gebäude 12 HRB 77719
13355 Berlin, Germany Amtsgericht Charlottenburg
Tel.: +49 30 23 45 86 96 Sitz der Gesellschaft: Berlin
Fax: +49 30 23 45 86 95 Geschäftsführer: Olaf Wagner
Received on 2008-02-04 13:30:12 CET