On Fri, Feb 24, 2006 at 11:00:50AM -0500, Phillip Susi wrote:
> You really can't share a wc between multiple users. Obviously they can
> try to edit the same file and clobber each other, and when they do go to
> do a commit to the repository, the repository won't know who actually
> did the commit. Also if two people try to commit, update, revert, or
> whatever at the same time, you're going to clobber the wc.
Well, you can, but it all depends on what the use pattern is. An example
is that for a project I'm working on, we have a WC of the website as the
docroot on the webserver. Anyone related to the project can go in and
make changes to the WC and commit from there. This isn't a huge issue
because there are only 4-8 people who could make changes, and we do
so very rarely (the website isn't the product we're working on), so we
don't worry about the issues of multiple people editing the same file,
different operations running at the same time, etc.
In the end, my opinion is that if there's going to be any form of
complexity wrt how people do their work, there should be separate WC
per user. Disk is cheap. :)
BTW: "the repository won't know who actually did the commit" -- sure it
will, assuming the users don't su/sudo to run the commands. It read as if
they are simply sharing the WC via group/permissions as opposed to having a
"group user" that people switch to so they can make edits.
> IIRC, shell scripts can not be suid, only binaries can.
It depends on the OS actually.
Randomly Generated Tagline:
"Depends on how you define 'always'. :-)" - Larry Wall
Received on Fri Feb 24 17:46:17 2006
- application/pgp-signature attachment: stored