Scott,
This still would not solve your problem as the hook script would have
no knowledge if the correct "-r xxx" parameter was used, only that a
"-r xxx" parameter existed.
Rather than using the -r xxx we use a URL that is a "tag" and have
hook scripts that prevent changes to tags. This does not completely
solve the problem, but prevents a developer from committing changes to
the external working copy from within a different working copy.
No matter what you do, it will always be the person committing the
changes responsibility to ensure the correct "-r xxx" or tag URL is
used for svn:externals.
Paul
On 1/30/07, Scott Nicolson <Scott.Nicolson@oscmar.co.nz> wrote:
>
>
> > I can see you reasons for doing this and as always it's a matter of
> > preference. Our strategy is to continually integrate changes from
> > dependencies into the mainline. When a release is made, the release
> > branch has the dependencies stabilised using the -r flag.
> >
> > This shifts the manual burden to the release process but gives you the
> > confidence factor for your release branches while allowing continuous
> > integration on the main line.
>
> Is it possible to create a hook script that mandates all externals
> within a release directory are fixed using the -r? This will greatly
> minimize user error when releasing code. If it is possible to create
> this hook script, do you know if anyone has done it?
>
> Scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Jan 31 00:46:24 2007