[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Web projects, commit problems & repository access

From: Philip Reynolds <phil_at_Redbrick.DCU.IE>
Date: 2003-02-13 22:00:53 CET

I have currently been mucking around with subversion for a while, as
a lone developer. It's quite neat.

At the moment, however, I'm looking into letting subversion manage a
web project (reasonably small, ~= 250k)

What I want (ideally) is to have a webtree at:

        /usr/local/www/myproject/

which is a checked out version of the project. This is the webtree,
so in this sense, this checked out version is never removed and
always exists. Files are directly edited here and committed, or
added then committed.

All this seems fine for a single developer, but as multiple
developers come along, I think this idea melts.

As there is only one checked out version of the source, two people
cannot reliably edit the same file at the same time. This could lead
to file overwriting, possibly corruption and at the very least
bypass subversions versioning model.

Checking out the source in our home directories, would mean that
changes go to the source first, which are then committed but then
have to be checked out on the main source page then. This is rather
cumbersome, especially in the development of a new system, where
changes are constantly being made.

What alternatives have people had with this?

One minor problem I've run into, is with using ``svn commit''. It
seems to leave a svm-commit-XXX.tmp file in the current directory,
if you allow it to open up an editor to create the commit message.
I can bypass this little problem by using the ``-m'' flag, but it's
rather annoying all the same. TMPDIR is set in my environment and
I'm currently using svn version:

        svn, version 0.16.0 (r3987)
                   compiled Feb 7 2003, 14:28:10

on FreeBSD 4.7-STABLE

Ok, one last problem I can't seem to fix, is the issue where
``user1'' creates a repository (svnadmin create) and wants to allow
``user2'' full access to it (adding, reverting, deleting,
commiting).

In this situation, both users will be using checked out versions on
the same machine, so we're using file:/// URL's to access the
repository. I can only presume this is done using UNIX file
permissions, however I can't see this described anywhere.
Perhaps someone could shed some light on this.

Apologies if these questions are answered somewhere, I've read the
excellent ``Subversion: The definitive Guide'' by Ben
Collins-Sussman, Brian W. Fitzpatrick, and C. Michael Pilato and the
FAQ to no avail. Searching the mailing lists didn't seem to crop up
much either. Feel free to point out documentation or information
I've missed somewhere.

Regards,

-- 
  Philip Reynolds        
   RFC Networks          tel: 01 8832063
www.rfc-networks.ie      fax: 01 8832041
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 13 22:01:36 2003

This is an archived mail posted to the Subversion Dev mailing list.