I'd like to upgrade our version control from CVS to Subversion. However, we
have an unusual (I think) setup which I don't know if subversion will work
with. Can anyone comment?
(i) Our (linux) system includes several services and absolute paths. Instead
of each developer working on their own working-copy in their own directory,
each box has one copy of the system in a specific directory. All services
are up and running continuously and are only restarted if the developer
requires it.
(ii) We do extreme programming, and as such everyone shares machines. This
means that from one day to the next there will be different users working on
any given machine.
(iii) We don't want to use a shared username (it violates company policy)
With CVS, we have this setup by every username being in the same group. If I
begin using a machine and checkout/commit code then the next day any other
user can continue on the same machine. If necessary, they can continue with
any changes I've made but haven't yet committed (but in theory I will have
committed all my changes by now anyway). Whenever anyone commits (or
updates) they will use their own username so we have a record of who did
what and why. Just in case anyone manages to get files with the wrong
permissions we have a script that resets everything back to a working (from
a file permissions point of view) state.
We have just tried a similar system with Subversion but got lots of
permission and operation denied errors despite several attempts at changing
file permissions. Does anyone know if this setup is likely to even be
possible with svn or is it a requirement that each user works in their own
working directory?
Thanks,
Brian
Received on Wed Jan 5 11:14:43 2005