You could create a custom property on the directory (svn ps glong:released 'WHATEVER INFO YOU WANT') and then and have a pre-commit hook that looks for the present of that property and refuses commits to those directories. You could also set attributes to read-only, but if they can't commit, it really doesn't matter.
I just plucked 'glong' from your email address: use something unique to your company name (NOT svn: tsvn: etc...) On Tue, Feb 15, 2011 at 09:33, Greg Long <subvers...@glong.info> wrote: > Hi, > I am supporting a Subversion repository that has a some interesting > requirements. > > - Log message minimum length. > - Files in release directories must not be changed or deleted. > - Files in template directories must not be copied. They should be > extracted instead. > > These I have all dealt with in a Python-based pre-commit hook. > > I am stuck on one last requirement. All files in release directories > should have the svn:needs-lock property. The real goal is not the > svn:needs-lock property, but the read-only status when a release > version is checked out. > > All released files are placed somewhere under a directory named > Rel, e.g., .../Rel/A10/20100215/ReleasedFiles.txt > > My first attempt was to force it in the pre-commit hook. This did not > work, because to create a release, we just copy a development branch > to a release directory. That means no files are changed, so the > pre-commit hook does not get a chance to change, or even check for, > the svn:needs-lock property. > > I also tried experimenting with the tsvn:autoprops property, but that > was also unsuccessful. > > I have come up with 2 solutions, but I am looking for a better one. > 1) Do not allow directories to be copied into release directories. > This would force the user to actually commit files. > 2) Use the script add-needs-lock.py which can do exactly what I need. > The problem is that it takes several minutes to run, so it cannot > be run during the commit process. This leaves open the possibility > (probability) that a release version could be checked out but the > files not marked read-only. > > Client: primarily TortoiseSVN 1.6.1x > Server: Apache 2.2 with svn 1.6.6? running on Windows XP > > Any assistance would be appreciated. > > Thank you, > Greg >
