Come to think of it how do the modules know where to locate the
subversion libraries? Is that path hardcoded into the modules? I have
two svn installations right now. 1.3.1 is installed in /usr/local and
1.3.2 installed property at /usr/local/svn-1.3.2/. Is there any way
to test to see which of those installations my apache modules are using?
Bradley
On Jun 4, 2006, at 6:30 PM, Bradley Wagner wrote:
> Hmm. I guess that's as good as it gets. Is DESTDIR the destination
> for the svn installation or the modules directory? Are the apache
> modules somehow linked to the location of the subversion
> installation. So if I go moving around the modules and removing the
> duplicate subversion install, will that mess anything up?
>
> Bradley
>
> On Jun 4, 2006, at 5:49 AM, Erik Huelsmann wrote:
>
>> On 6/2/06, Bradley Wagner <bradley.wagner@hannonhill.com> wrote:
>>> I have installed subversion already. The binaries are there and
>>> functioning correctly. Now I'd like to go back with the source the I
>>> kept and simply install the apache modules and nothing else. Is
>>> there
>>> any way to do this without overwriting my existing installation of
>>> the binaries and libraries? Is there any way to tell configure to
>>> only build the apache *.so files?
>>
>> No, but you could do a DESTDIR install (make install DESTDIR=....)
>> installing to another dir than the one your install is currently
>> located. After that, you can copy the apache modules to their real
>> directories and remove the destdir.
>>
>> HTH,
>>
>> Erik.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 5 00:44:07 2006