[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Anoncvs -> SVN
From:       Alan Chandler <alan () chandlerfamily ! org ! uk>
Date:       2005-04-01 19:00:01
Message-ID: 200504012000.01362.alan () chandlerfamily ! org ! uk
[Download RAW message or body]

On Friday 01 April 2005 18:45, Jonas Widarsson wrote:
> On Fridayen den 1 April 2005 19.08, Alan Chandler wrote:
> > Thats because svn supports two sorts of repositories.  Remote ones, and
> > local file based ones.  It is refering to either
> >
> > a) local file based ones, where the client side library is writing the
> > file, and could get corrupted when running across and nfs network, or
> >
> > b) the remote repository code, which then is writing to a local file on a
> > remote machine, which again must not work across a network
> >
> > This has NOTHING to do with an svn client (or a svk one) talking to the
> > remote kde repository across the network.
>
> I would say there is only one kind. It is always local. It is not meant to
> be distributed filesystemwise. That's why it is noted in the manual not to
> put the repository on a network mount. (due to locking mutex issues.)

Its how you use the words of course.  But I WAS talking with respect to the 
svn client


>
> The _repository_ is the same, regardless of access method. I think you
> mislead
>
> the reader when saying:
> > Thats because svn supports two sorts of repositories.  Remote ones, and
> > local file based ones.
>
> That is not literally true.

It is LITERALLY true - the svn client can use a URI of file:///some/path, in 
which case its accessing a local repository. 

Alternatively it can access a remote one via http://domain.com/path,   
https://domain.com/path, svn://domain.com/path, or svn+ssh://domain.com/path 
in which case the libraries on the client side use communications to 
establish a connection with another machine (actually you can use localhost) 
running the server software

>
> However, repositories are remotely accessible thanks to svnserve, which
> provides a special svn protocol which in turn runs over either "http" or
> "svn+ssh".

This is not strictly correct.  http is http, https is http with ssl 
encryption, svn is a specialist protocol for svn and svn+ssh is svn tunnelled 
through ssh.  svnserve only supports the svn protocol, you use mod_dav and 
mod_dav_svn modules with apache to get the http protocol support.

>
> Any repository is created with "svnadmin create" regardless of whether you
> intend to run it locally only or serve it with svnserve as well. And the
> switches available to "svnadmin create" have nothing to do with the
> conceptual difference between local or remote.


Absolutely - but then svnadmin is not the svn client, but another program that 
you have to run locally where your repository is located.  This is totally 
irrelvent to a kde developer accessing the kde repository.






-- 
Alan Chandler
http://www.chandlerfamily.org.uk
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]