On Thu, Aug 15, 2002 at 03:04:39PM -0400, Wilfredo Sanchez wrote:
> A comment about using and installing APR.
>
> Right now, if we install svn with --prefix=/usr/local, we park the
> db, neon, and apr libraries into /usr/local/lib and headers into
> /usr/local/include.
You are building those things, and you told SVN what prefix to use for
installation. That is simply the nature of things.
If you want different prefixes for the dependent items, then build/install
them *separately*. The fact that you can build them as subdirs of SVN is
simply a convenience.
[ personally, I build everything into /usr/local/svn/..., so I don't have
problem that you're seeing ]
>...
> So I would like to suggest that at least in the case where prefix is
> a standard path (/usr, /usr/local, /opt), that libraries go into
> someplace unique to SVN, such as /usr/local/lib/svn-<version>/ and
> /usr/local/include/svn-version/ so that you have to explicitly add
> these to your search paths to get them.
Nope. See above.
> I think that httpd is in the same boat here, by the way, and I don't
> think it's a good idea that we look for APR in /usr/local/apache2. The
That is a great place to find APR unless/until APR becomes more common as a
standard-install package.
> version of APR built for httpd 2.0 is meant for that build of Apache
> 2.0 and not svn or other software.
Not necessarily. We have facilities in APR (now) to specify a version and to
check that version. SVN will be moving to a model whereby we require a
specific version of APR, not just "what is available".
>...
> Note, however, that this is different for mod_dav_svn, which should
> use the same APR as httpd, since it's being linked into httpd. Hrm...
> Yeah, still think so. mod_dav_svn should use apxs to find the right
> APR for httpd, but the rest of svn shouldn't be bound to that version
> of APR. I should feel free to whack my httpd install without worrying
> about breaking the svn command line client, for example. Yeah, I might
> break the SVN server, but that's a given, since the server tied to
> httpd.
Actually, this is a horribly difficult problem. Yes, mod_dav_svn could or
should use httpd's copy. However, mod_dav_svn also uses SVN libraries. And
those are going to be built against something else...
IMO, the real answer is to install APR into a system location and configure
httpd to refer to that (instead of a builtin copy). Then SVN would also use
the same libraries.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 15 22:44:33 2002