Re: questions before switching from cvs to svn

On Tue, 18 May 2004, John Peacock wrote:

> All databases require special backup handling, since their files must be
> maintained as atomic units (as opposed to individual files like CVS).

In fact, I would like to avoid two backup mechanisms (ext3-dump and
database-backup). But perhaps, it's worth the effort, thank you.

> for different ways to maintain backups. In fact you should probably read
> through the whole book before proceeding much farther...

Before reading the whole book, I wanted to be sure, that subversion *can*
fit our needs. Now, I'm beginning to read it, the decision is taken in
favour of subversion.

> > * RW and RO access
> > In our cvs-repository we use POSIX-ACLs, that allows us to distinguish
> > read-only and read-write access for each project and each user.
> > In the FAQ-list (http://subversion.tigris.org/project_faq.html#readonly)
> > it seems to me, that this is not possible with subversion, is this correct?
>
> new revisions through various means. The easiest is probably
> authz_svn_module,
>
> You can also use svnserve and provide r/o and r/w users, but the support
> is much more limited:

Yes, there are apache and svnserve, but we would like to use our well
working ssh authentication. After reading a bit the 5th chapter, I've
finally found a method, that could fit our needs:
suid svn for files /usr/bin/svn and /usr/bin/svnserve and permissions 700
for the repository and owner svn. So only these two executables can access
the repository. Then, all subdirectories with permissions 770, files 660
with owner root and group svnusers.
With some custom commit-hook-script, we'll forbid write access in function
of author and directory, so we'll get the same as now with cvs: all people
in one group have ro access, rw only for special users.

Thanks for your answer, Peter

-- 
http://pmrb.free.fr/contact/
________________________________________________________________
FilmSearch engine with a lot of new features: http://f-s.sf.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org