On Sun, 2002-08-25 at 16:31, Stefan Schwarzer wrote:
> # TODO
> #
> # - Deal smarter with application workdir regarding re-installation
> # -> Currently, an _already existing_ application workdir ${WEBKIT_HOME_DIR}
> # is left untouched on de-installation and re-installation in order to
> # preserve old configuration settings. However, this will cause problems
> # when new Webware versions become incompatible with old configuration
> # files. Moreover, the CGI script WebKit.cgi and OneShot.cgi won't be
> # updated in the current port version.
> #
> # How should I deal with that? Do you have any suggestions?
Configuration shouldn't be a big problem, as unspecified configuration
values will be set to the default (as defined directly in the
configurable class itself). It might be useful if, say, there were a
way to show configuration values that were not set, so a person could
update their configurations if they don't like a default for a new
setting. But not a huge deal.
WebKit.cgi and OneShot.cgi are very stable, AFAIK. They don't do much
work themselves, and the work they do hasn't changed for some time.
Mostly they are a wrapper for Adapter.py -- CGI itself hasn't and won't
change, and the interface for Adapter probably won't change much either
(even as the internals do change).
It might be useful to include some version information in the workdir
stuff, so future backward incompatibilities can at least show a useful
error (e.g., "You must update your settings, see /usr/share/doc/SETTINGS
for more information"). This might already be embedded somewhere, I
don't know.
Ian
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
