On Tue, Aug 09, 2005, Christoph Schug wrote:
> [...]
> subversion is picky about versions hence make it happy by by providing
> its own neon library with the most wanted version number
> [...]
> +%define V_neon 0.24.7
> [...]
> %setup -q -T -D -a 1
> + %setup -q -T -D -a 5
> + mv neon-%{V_neon} neon
> %patch -p0
>
> # substitute path from applied patch
> @@ -142,7 +146,7 @@
> ./configure \
> --prefix=%{l_prefix} \
> --with-berkeley-db=%{l_prefix} \
> - --with-neon=%{l_prefix} \
> + --with-ssl \
> --with-zlib \
> --enable-static \
> %if "%{with_perl}" == "yes" || "%{with_python}" == "yes"
This I don't understand, Christoph. Subversion 1.2.1 already contains
a local copy of exactly Neon 0.24.7 in its subdir neon/. What you are
doing here seems like adding another unnecessary copy into neon/neon/.
I've backed out this part of your patch now as the local copy contained
in the Subversion 1.2.1 tarball is already sufficient. Additionally,
I've now removed the NEON installation files, as I don't see why
Subversion needs them under its run-time.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [email protected]
