[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Modifying file properties in pre-commit

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Sat, 13 Sep 2008 20:11:05 -0500

On Sep 13, 2008, at 6:53 PM, Lira Olavo wrote:

> Blair Zajac wrote:
>> Purple Streak wrote:
>>> Lira Olavo wrote:
>>>> Yes but isn't it the same as working within a team? It is like you
>>>> commit something and then someone after you commit a new
>>>> version, so
>>>> your version now is not up-to-date. Why would you call it "break
>>>> the
>>>> checkout"?
>>> The difference is probably when you do an update the client doesn't
>>> know something has changed in the revision it committed and so
>>> doesn't
>>> download that change? I'm guessing here as I'm new to subversion
>>> and
>>> trying to learn it all fast :)
>> Right.
> Thank you all for the answer also, pin the TAG is also my problem
> but I
> can't control all the clients for witch SVN Gui they are using,
> sometimes is subversive, others, subclipse, sventon, tortoise and ant
> svn... How can I impose the pin of a svn:externals during a TAG for
> all
> my clients then?

Write a pre-commit hook. The logic would be something like:

Check "svnlook dirs-changed" on the incoming transaction. If
something is being added in the tags directory, then check every
subdirectory of the thing being added for the presence of the
svn:externals property. If it exists, check to make sure the value
contains "-r N" where N is an integer. If it doesn't, print an error
to stderr explaining to the user that they need to use svncopy.pl and
exit with a nonzero value.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-14 03:12:46 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.