Howard wrote:
> In this regard, I wonder of some system of patches, at least for the
> setup and configuration files, might make sense? Most ``modern'' software
> control systems (e.g., CVS), and even archivers (e.g., arc) store past
> versions or multiple versions as ``patches'' -- files that change what
> part of a file has changed, and leave alone those lines or parts that
> have not changed. This allows compact storage of a series of updates,
> and retrieval of any particular update, if desired.
I have two comments:
1. Arachne doesn't use a CVS (but Michael has said he is going to set one
up for over 6 months now <g>)
2. This is completly possible now without using any external programs
(external to Arachne that is). The simple answer, which Clarence will
disslike, is to make an upgrade APM for each version. The problem, as with
many other things, is the time - or lack there off. It would after all
take a while - especially when several files have changed, or new
configuration options are present. There's also the risk that Michael will
forget some small detail that is important and thereby the upgrade
wouldn't go "all the way". Additionally I think that it's better that as
many as possible use the wizards each time, that way any bugs/problems can
be fixed (or located anyway) faster.
//Bernie
http://bernie.arachne.cz/
