You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by ar...@betasystems.com on 2004/09/27 13:58:15 UTC

Installation Issue on SuSE Linux Enterprise Server 9 (sles9)




Hello everyone,

has anybody any experience installing svn on SuSE Linux Enterprise Server 9
with the Apach2.0.49 rpm package comming with it?

If I install the latest svn 1.1.rc4 with a seperate installation of the
latest apache 2.0.51, all goes fine,
but if I specify the ./configure with:

--with-apache=/etc/apache2 (that's the standard path on suse and the
modules are under /usr/lib/apache2-prefork)

I would get some errors and the mod_dav_svn and mod_authz_svn couldn't be
build.

--> the solution or workaround was to build svn without sles9 and then copy
the modules manually to apache2-prefork folder of the suse installation.

now my cheef doesn't like this solution and he is afraid, that some side
effects could arise in the future on the production server.

any ideas how to make my cheef lucky? :-)

Best Regards,
Arash


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Installation Issue on SuSE Linux Enterprise Server 9 (sles9)

Posted by Peter Poeml <po...@suse.de>.
On Mon, Sep 27, 2004 at 03:58:15PM +0200, ark-d@betasystems.com wrote:
> has anybody any experience installing svn on SuSE Linux Enterprise Server 9
> with the Apach2.0.49 rpm package comming with it?
> 
> If I install the latest svn 1.1.rc4 with a seperate installation of the
> latest apache 2.0.51, all goes fine,
> but if I specify the ./configure with:
> 
> --with-apache=/etc/apache2 (that's the standard path on suse and the
> modules are under /usr/lib/apache2-prefork)
> 
> I would get some errors and the mod_dav_svn and mod_authz_svn couldn't be
> build.

Which kind of errors? 

> --> the solution or workaround was to build svn without sles9 and then copy
> the modules manually to apache2-prefork folder of the suse installation.
> 
> now my cheef doesn't like this solution and he is afraid, that some side
> effects could arise in the future on the production server.
> 
> any ideas how to make my cheef lucky? :-)
> 
> Best Regards,
> Arash

Peter

-- 
Thought is limitation. Free your mind.