[daisy] Re: Upgrade from 1.5 to 2.0: wrapper issues withlogkit.xml

[Robert Kindl]

> > > > IMHO config files for wrapper are little bit broken (including .bat
> > files)
> > > Could you comment some more on the problems with the bat files?
> >
> > daisy-startup.bat is calling DaisyRepo.bat and DaisyWiku.bat which got
> > renamed.
> > Then it's calling ..\..\resources\sleep.bat and
> > ..\..\resources\T4ePortPing.exe which doesn't make it in final release
at
> > all ;-)
>
> I think is is a misunderstanding:
> When upgrading from a daisy instance that was got using the
> windows-installer, one should not rename c:\Program Files\Daisy-1.5.1
> (or whatever the main directory was named), but the directory
> c:\Program Files\Daisy-1.5.1\daisyhome. The new DAISY_HOME directory
> could then be somenthing like c:\Program Files\Daisy-1.5.1\daisyhome2
> (or so). This way, the port ping utilities and everything else are
> still in place and functional. I just tried an upgrade from an 1.5.1
> instance in that way and the wrapper scripts were working flawflessy
> after the upgrade, without any manual intervention. Despite of that
> fact, I would like to see the wrapper scripts and config file
> distributed with Daisy 2.0 used for starting up daisy as service.

So these utilities are available only if you already have previosly
installed 1.5 version?
IMHO Daisy 2.0 package should contain everything needed and should in no way
depend on fact if it's upgrade or not.

> > Main problem with daisy-repository-server-service.bat and
> > daisy-repository-server-service.bat
> > is that it doesn't find wrapper conf files (it's looking for them in
same
> > directory as wrapper.exe).
>
> That's correct. These files are templates only, to be copied in the
> service directories of the daisy wiki and daisy data wiki dirs (to be
> created when updating. We really should add a README.txt (or as
> already proposed a DO_NOT_USE_THESE_SCRIPTS.txt) file with the daisy
> 2.0.1 release.

Personally I would rather read
"THESE_SCRIPTS_ARE_READY_TO_USE_OUT_OF_THE_BOX.txt" :-)

I don't see any real problem in making them working (except some work which
already has been almost done).

Rob