You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ben Collins-Sussman <su...@collab.net> on 2004/08/02 12:46:40 UTC

Re: Remote use of SVN

On Mon, 2004-08-02 at 04:27, Markuz Makkonen wrote:
> Thanks for the help Ben.

[Please keep your repsonses cc'd to the users@ list]

> 
> I'm having a little problem with 'make install'-part, since i don't have
> write permissions to '/usr/local/'-folder. So basicly u have to be root to
> install SVN client  even though u just wan't to use a repository over SSL
> (https)?

Not at all.  You just need to tell ./configure that you plan to install
stuff in your home directory, not in a global system directory.

   ./configure --prefix=/home/username

The is the way almost all "./configure; make" software works.  I get the
impression that you don't have much experience building software.  :-) 
You might want to consider grabbing some precompiled binaries for your
system -- perhaps someone can even give you a statically linked client
binary, since that's all you need.

> 
> Aww...I wish there was a way to get the client working with less priviledges.
> 
> -Markus
> 
> 
> 
> if [ ! -d /usr/local/apr/include/apr-0 ]; then \
>     /tmp/svn/subversion-1.0.6/apr/build/mkdir.sh
>     /usr/local/apr/include/apr-0; \fi;
> mkdir /usr/local/apr
> mkdir: cannot create directory `/usr/local/apr': Permission denied
> mkdir /usr/local/apr/include
> mkdir: cannot create directory `/usr/local/apr/include': No such file or
> directory
> mkdir /usr/local/apr/include/apr-0
> mkdir: cannot create directory `/usr/local/apr/include/apr-0': No such file
> or directory
> make[1]: *** [install] Error 1
> make[1]: Leaving directory `/tmp/svn/subversion-1.0.6/apr'
> make: *** [external-install] Error 1
> 
> 
> > On Thu, 2004-07-29 at 07:01, Markuz Makkonen wrote:
> >> Hey,
> >>
> >> I've Subversion 1.0.6 set up with https://-schema on Linux.
> >>
> >> Do all the remote users connecting their repositories need to
> >> compile/install a svn client on their local machines in case they want
> >> to
>  commit changes etc.?
> >
> > Yes, to checkout a working copy from an svn server, you need an svn
> > client.
> >
> >>
> >> What command(s) to use with the source for building just the client to
> >> be
>  able to work remotely over https://-schema? Or is there any easier
> >> way to
>  enable svn remote connections on client side?
> >
> > (unpack svn tarball)
> > ../configure --with-ssl
> > make
> > make install
> >
> >
> >
> 
> 


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