Hi,
I'm currently struggling to get multiple users working on the same checkout.
I know, this sounds a bit wierd, the reason is:
the check out is done onto a specific share (working under windows,
using tortoise). This share is actually a linux machine, with samba und
apache. Apache is configured that this specific directory is the
documentroot for a certain virtualhost. This is only our development
environment, of course.
Since some projects require specific apache/database/scripting language
options, it was choosen to hold the checkout we work on in the same
place so we have a cerntral development platform which is tuned for our
needs and not every project member needs his own complete development
environment. We can exclude that two people work on the same file
simultaniously, still we want a revision of every major changes commited
to the repository.
The problem I've seen so far was:
- subversion/tortoise removes any write permissions from files in .svn.
Thus, only the file owner can modify them.
- I tried to force with samba so always write permissions are set,
however I had strange locking issues and still write permission problems
(though I was unable to analyse why; unix permission _seemed_ fine to me).
I would favour hints/suggestions on how to fix the permission issue,
however other suggestion on how we could modify our development
environment so we don't have the permission problem are also welcome.
The main reason was to not duplicate the server settings environment and
speed up testing phases (it's about web projects) so files are always
directly available to apache.
thanks,
- Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 20 12:25:11 2004