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

Re: Rebundling TSVN

From: Michael Jervis <michael.jervis_at_cse-servelec.com>
Date: 2006-02-08 15:14:41 CET

>To get the model you want, you need to set every file so it has the
>svn:needs-lock property set true - this will make all files read-only
>when your developers check out working copies, and they will be advised
>that to make changes, they need to get the lock on the files they want
>to change.

Yes, I'm aware of this.

When importing the code, we are setting this flag for all existing code
modules. We also have a hook script in place that will block the commit of
any file that does not have svn:needs-lock or svn:keywords including Id in

However, this is going to be a frustrating experience when adding new files,
several stages of reject to get through. Thus the plan was to install config
on each developers machine to include auto-props for the two properties,
plus a few other little tweaks we may include.

Now, I could ask the developers to install the TSVN installer, then apply
the localconfig.exe installer, but I'd rather make it a one step MSI to
install the whole lot (so they don't get nosey too!)

>You could also maybe use Orca (from the MS platform SDK) to edit the
>content of the MSI to insert your own config file - but I don't know
>much about that.

That was more what I was hoping to do, can Orca rebuild an MSI without
VS2005 installed? That's the problem I have at the moment, I can't build the
installer (or edit it easily) as we don't have VS2005.



To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Feb 8 15:14:53 2006

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

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