🚀 go-pugleaf

Hi there Paul, I believe it was you who said:
>>Hi there Terrance, I believe it was you who said:
>>> Neil Bothwick (neil@wirenet.u-net.com) wrote:

>>>> > I just unarced it... And copied any new classes over...
>>>> 
>>>> Me too, by clicking on the installer icon ;) The ClassAct part of the
>>>> installation is a standard installer script supplied by the ClassAct
>>>> author to all developers, so it /should/ work on all machines.

>>> I'll have a look through it then, it's just I don't trust people to check
>>> versions properly... And even when they do, I like to take a backup of
>>> any individual files that have been replaced just in case (and it proved
>>> useful this time...)

>>I know what you mean, I always do a backup before running any
>>installer that messes with system directories, and I have SnoopDos
>>logging to a file. But I did have a look at the ClassAct installer
>>first, and it uses copylib, which does check versions. It's when they
>>use copyfiles for system files that you worry.

> I basically examine all the system files in the program that I am about to
> install and if I have say a newer version of a library i just copy my librar
> over their old one.  It used to be very annoying having some crap 3 year old
> library being installed over a nice new one!  - also all my libraries etc ar
> protected....

Just look through the script to see which command it uses to copy
system files. Copylib does version checking, so it can't overwrite
newer files with old ones. But if it uses copyfiles, then beware, the
script writer probably went to the Omnipresence School of Programming :(


Neil
--

 |           Neil Bothwick, Warrington, England           |
 |--------------------------------------------------------|
    Facts are stubborn little bastards, be careful with
                           them.