You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Alejandro Lopez Rama <al...@gmail.com> on 2008/03/11 12:36:37 UTC
Evaluating Subversion
Hi, we're analyzing Subversion to manage our source code versions. Do you
some easy manuals to start with it?.
One of the issues we need is to have the last version of each component
available (for read-only purposes) out of the repository.
Is is available?
Thanks in advance
--
Alejandro Lopez Rama
Re: Evaluating Subversion
Posted by Marc Haisenko <ha...@comdasys.com>.
On Tuesday 11 March 2008, Alejandro Lopez Rama wrote:
> Hi, we're analyzing Subversion to manage our source code versions. Do you
> some easy manuals to start with it?.
> One of the issues we need is to have the last version of each component
> available (for read-only purposes) out of the repository.
>
> Is is available?
>
> Thanks in advance
http://svnbook.red-bean.com
--
Marc Haisenko
Comdasys AG
Rüdesheimer Str. 7
80686 München
Germany
Tel.: +49 (0)89 548 433 321
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Evaluating Subversion
Posted by Thomas Harold <tg...@tgharold.com>.
Alejandro Lopez Rama wrote:
> Hi, we're analyzing Subversion to manage our source code versions. Do
> you some easy manuals to start with it?.
> One of the issues we need is to have the last version of each component
> available (for read-only purposes) out of the repository.
Lots of ways of doing this...
- You could setup Apache in a WebDAV setup in read-only mode so that
users or tools could mount the SVN repository as a drive. (I haven't
personally tried that.)
- You could use systems like ViewVC or other repository browsers to
provide a read-only HTTP interface to the repository.
- You could setup a read-only user and have the tool use that to keep a
read-only working copy on a local disk. It wouldn't be as immediate as
some of the other options. You would just need to run "svn update" on
the tool's working copy before using it.
I'm sure there's a few other methods that I can't think of off-hand.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Evaluating Subversion
Posted by Toby Thain <to...@telegraphics.com.au>.
On 11-Mar-08, at 8:36 AM, Alejandro Lopez Rama wrote:
> Hi, we're analyzing Subversion to manage our source code versions.
> Do you some easy manuals to start with it?.
http://svnbook.red-bean.com/
> One of the issues we need is to have the last version of each
> component available (for read-only purposes) out of the repository.
Very easy.
>
> Is is available?
>
> Thanks in advance
> --
> Alejandro Lopez Rama
>