Sorry for the last e-mail that ended mid-sentence; I hit Ctrl+Enter by
accident.
> So I have this:
> /trunk/
> -------RealContent
> -------file1.txt
> /mirrored/
> ----------staged/RealContent
> ----------live/ver-1/RealContent
> ----------live/ver-2/RealContent
> ----------live/ver-3/RealContent
(..snip..)
> Therefore, I want to restrict any 'svn copy' commands to '/mirrored/live'
> to only allow a copy from '/mirrored/staged'
(..snip..)
I'm not sure I understand everything you're trying to do (the remote
repository stuff is a little ambiguous), but it sounds like you want there
to be a controlled release process. Since the sensitive destinations are
under a common folder (/mirrored/live/), I would suggest considering the use
of authz to restrict who can commit to that part of the repository and using
a special script (invoked from, say, a web page) that performs a copy from
/mirrored/staged/ once the required conditions are met. That script could
also enforce a naming convention and use the credentials of the only user
allowed to commit to that area.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Olivier Dagenais
Software Engineering / Génie logiciel
Formark - Combine the Best of SharePoint® and Livelink®
Phone: 613-599-5173 ext 238
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Make sure you don't miss anything: subscribe to the Formark Newsletter:
http://www.formark.com/support/register/index.asp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 9 00:43:00 2007