Enno Rehling wrote:
> I know that. Beleive me, I know that... We had a long discussion about
> the whole thing, and it fails. It's the way people in that department
> have always worked. All their process and tools are built around that
> way of working.
>
> We want the stuff they produced in our asset control, which is why we're
> making them use subversion. To the rest of us, that whole department is
> basically one user, because of the way they work. However, to samba,
> they are not just one user - and our network department is refusing to
> let them all be one samba user either.
It sounds to me that this department is just way too inflexible to be
migrated to version control, so I would suggest that you hide it from
them. Let this department just access the working copy as a samba
shared directory and tell them never to use any subversion commands.
Then have some cron script run every so often on the server that does
svn status, svn add, and svn ci as necessary. That way this problem
department gets to act like they're not being version controlled, and
they won't even need to be given read access to the .svn dirs, and you
get to see their content checked in to your repository with whatever
frequency you want.
The disadvantage of this method is that you of course lose the
concurrent access protections that subversion gives you, but it sounds
like this isn't an option for this department anyway.
The advantage is that on the samba side, it's pretty much just as easy
to configure as any shared dir and the access controls can follow
whatever policies that your network department wants. On the svn side,
the whole department looks like the single user that the cron script
executes as.
-Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 14 20:55:44 2004