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

RE: Re: Need checkout commits...

From: Thompson, Graeme (AELE) <Graeme.Thompson_at_smiths-aerospace.com>
Date: 2005-12-12 13:01:29 CET

I have just tried this with a subversion 1.2.3 server on SUSE 10 and a
TortoiseSVN 1.2.6 client.

It does not *Require* you to have a lock in order to commit a file with
the svn:needs-lock property. You can simply make the file writable and
then do a commit and it will happily go ahead and update the repository.

Is there any way to get this to be a requirement, e.g. through a
pre-commit hook similar to the suggested one to ensure that all files
have the svn:needs-lock property set?

If so then has anyone got any examples of how to do this?

Thanks,

Graeme

> -----Original Message-----
> From: Lieven Govaerts [mailto:lgo@mobsol.be]
> Sent: 12 December 2005 10:34
> To: maxx@eureca.ru
> Cc: Subversion
> Subject: Re: Need checkout commits...
>
> I suppose you mean for some type of files you need exclusive write-
> access?
>
> You can use locking for that:
> http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html
>
> Set the needs-lock property to value '*' on all your office files,
> so users are obligated to get a lock on this file first before
> they are able to change it. ( Similar to VSS Checkout operation ).
> The files containing this property will be read-only.
> ( this is a client operation, not server side )
>
> To make this easy for all your users, create a registry file
> with lines
> like this:
>
> ------------------------------------------
> REGEDIT4
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Tigris.org\Subversion\Config\miscellany]
> "enable-auto-props"="yes"
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Tigris.org\Subversion\Config\auto-props]
> "*.doc"="svn:needs-lock=true"
> "*.dot"="svn:needs-lock=true"
> "*.exe"="svn:needs-lock=true"
>
> [HKEY_CURRENT_USER\Software\TortoiseSVN]
> "CheckNewer"=dword:00000000
> --------------------------------------------
>
> Add lines like "*.zip"="svn:needs-lock=true" for all extensions you
> need your users to lock first.
>
> Make them install this file after they install TortoiseSVN and you're
> good to go.
>
> hope this helps,
>
> Lieven.
>
> Quoting Maxx <maxx@eureca.ru>:
>
> > Hello!
> >
> > We migrate from Visual SourceSafe to Subversion.
> > So i must configure subversion for our users:
> > a file will block when file is checkout. It is
> > need because half of repository files are in
> > Microsoft Office format. I try to do this by hook
> > scripts. But i appear that hook scripts exist only
> > for modify events:
> >
> > http://svn.haxx.se/users/archive-2004-07/0865.shtml
> > > We generally only have hooks for write operations, not read.
> > >
> > > If you post saying exactly what you're trying to do,
> maybe someone can
> > > think of another way.
> > >
> > > -Karl
> >
> > So how can i solve my problem? Can i block file in repository by
> > hooks?
> > Somebody can say that i can execute two commands: checkout
> and block.
> > But as client we used TortoiseSVN, not a command line. Therefore i
> > want to solve my problem on server side.
> >
> > Thank you.
> >
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 12 13:06:02 2005

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