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

RE: Re: Rebundling TSVN

From: Peter Mounce <Peter.Mounce_at_whitbybird.com>
Date: 2006-02-08 15:31:46 CET

> -----Original Message-----
> From: Michael Jervis [mailto:michael.jervis@cse-servelec.com]

> 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 place.
> 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.

I agree. Vote for the repo-defined autoprops feature on the SVN
roadmap/issue-tracker ;-)

> 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.

You don't need VS2005 to build an MSI with WiX. The only reason there's
a .wixproj in there is because the WiX people provide a tool that allows
integration of WiX into VS2005. Rebuilding the MSI can be done with the
command line tools available from http://wix.sf.net - see our build
process in the TortoiseSVNSetup directory of the TSVN repo.

The build uses NAnt, but you should be able to use the same commands it
does, on your own unpackaged version.

See /trunk/src/TortoiseSVNSetup/setup.build lines 77 through 94.

You might find it simpler(!) to get a build environment set up, rather
than recreate the directory structure and then put files from the
extracted-with-Orca installer into the right places?

Over here, we have the same problem, but it's a small enough team that
we can just copy/paste the config file to everyone any time someone
changes it... Changes aren't that frequent nowadays (four months after
I introduced SVN+TSVN here).


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:32:03 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.