On Friday 18 Feb 2005 04:05, Ben Collins-Sussman wrote:
> On Feb 17, 2005, at 1:02 PM, Nick Brown wrote:
> > SVN_DB_INCLUDES is no longer used, and should thus be removed from
> > svn-config.in, so that svn-config works. Currently "svn-config
> > --includes"
> > produces useless output.
> >
> > svn-config --includes
> > -I/usr/include/subversion-1 -I/usr/include/neon @SVN_DB_INCLUDES@
> > -I/usr/include/apr-0 -I/usr/include/apr-0
>
> svn-config has never worked correctly, ever. We stopped installing it
> (in 'make install') nearly two years ago. Are you running a really
> old svn?
>
> See issue 751.
It must be my distribution.
Mandrake 10.1 (and the development tree "cooker") still install svn-config;
http://rpms.mandrakeclub.com/rpms/mandrake/devel/cooker/i586/media/contrib/libsubversion1_0-devel-1.1.3-8mdk.i586.html
The kde svn ioslave also makes use of it;
http://webcvs.kde.org/kdesdk/kioslave/svn/configure.in.in?rev=1.10&view=markup
So on my system the configure script for kde finds svn-config and uses it to
get things like --include. However --include produces garbage.
I'll take up the problem with both these sources.
Can I suggest to don't even include svn-config in the subversion source
distribution, to prevent people accidently installing/using it?
Cheers,
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 18 13:37:57 2005