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

[TSVN] Re: Re: Re: Re: Re: Nightly build readme.txt

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-10-25 11:19:03 CEST

"SteveKing" wrote:
> > Checking dll versions is not good! That's why we have an installer
to do
> > it for us ;-) I think this could lead to more email from confused
> > Now they avoid a reboot, but will it work?
> What I meant was: _you_ should check that if the last nightly build
> was installed correctly. Not that every user would have to do that.
> I think
> people using the nightly builds are skilled enough to determine if the
> installation went well or if they need to
> uninstall/(reboot)/install/reboot to make it work.

Yes they are, as long as the process is clear and they know what they
have to do. What I am trying to get to is an accurate text to put in the
readme that accompanies the nightly. Before the recent change it was
very clear but also very slow due to reboots. Now it is (normally)
faster, but less clear. See if this summary is correct now:

Uninstall/repair will not come up any more because product ID changes on
every build, so the only way to uninstall now is via control panel.

There is normally no need to uninstall before installing a nightly
Install new msi.
Log off & Log on.
Check TortoiseSVN.dll version.
If version is same as nightly, then all is OK, no need to reboot.
If version is wrong, do I:
a) just reboot?
b) uninstall, reinstall, reboot?

One other question. I say in the readme that TSVN nightly is always
built against released or RC subversion libs. SVN 1.2 will introduce
locking which might mean a major addition to the UI, and I guess you are
likely to start looking at this before 1.2.0RC1. Should I remove that


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 25 15:49:56 2004

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

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