[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: Peter Mounce <Peter.Mounce_at_whitbybird.com>
Date: 2006-02-08 14:18:02 CET

> -----Original Message-----
> From: Michael Jervis [mailto:michael.jervis@cse-servelec.com]
> Sent: 08 February 2006 13:00
> To: users@tortoisesvn.tigris.org
> Subject: Rebundling TSVN
> Hi,
> We are in the progress of making the VSS to SVN switch, and
> this will include rolling out TSVN to all developer machines.
> To ease us into using the SVN solution, we want to enforce
> certain config.
> Which as none of our developers have SVN experience will just
> be a case of putting various client config in place. (Just
> initially, as we move forward and people get used to the
> edit-merge-commit model we'll ease them back
> out.)
> I was thinking the best way to acheive this would be to
> rebundle the installer so it includes our settings.
> However. I have no VS2005, so I can't rebuild the MSI easily.
> Is it still possible to package with other installers? (I've
> picked up that once upon a time it was installed with
> innosetup). Are the old installers sources still relevant to
> the latest build? Anyone got other suggestions?

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.

See the TSVN manual, section 5.18.

In TSVN, this is achieved by TSVN|Settings|Edit Config. However,
there's no mechanism to do this centrally - it's a feature that's marked
on the Subversion roadmap (repository-defined autoprops -
http://subversion.tigris.org/roadmap.html). In the meantime, your
developers will have to tell each other if they change it, so they can
all be on the same page.

What you _could_ do is store the config in a repository, and then teach
developers to update it regularly. Or write a scheduled task to do an
svn update on it every x days or whatever.

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.


To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Feb 8 14:18:18 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.