Ah, ok. Yeah that would be a good way to do it. Maybe I will try that.
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006Q1@ryandesign.com]
Sent: Thursday, March 23, 2006 12:19 PM
To: Mark Johnson
Cc: users@subversion.tigris.org
Subject: Re: Which Method? What Tools? Ideas please.
On Mar 23, 2006, at 19:44, Mark Johnson wrote:
>>> Designer types using webdav tend to flood the repository with tons
>>> of trivial commits, but the only way around this is to install dev
>>> environments on their local machines too, which is still a
>>> frightening prospect.
>>
>> The other way around this (which is what we do) is to have people use
>> a working copy which is located in their public_html directory on the
>> central development server, to which they connect over Samba or
>> AppleShare or whatever and from which they can then commit and update
>> using whatever Subversion interface they have on their machine.
>
> I had been doing this for a short time, but this is really taking a
> step
> back because people can still overwrite each other without the
> possibility of locking or merging the overwritten versions.
No, they cannot. Each user has their own working copy (or even more
than one, if desired) in their own public_html directory in their own
home directory on the server. It's just the same as if the working
copy were locally on their own computer, with the added benefit that
the system administrator has only a single central Apache / PHP /
MySQL / whatever server to maintain instead of having to maintain all
that separately on each user's desktop machine.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 23 21:29:02 2006