NOTE: If you are a developer, please use a private wiki based on foswiki/trunk on a daily base ...or use
trunk.foswiki.org to view this page for some minimal testing.
Use
Item9693 for docu changes for 1.2 and 2.0.
Item10616: When installing an extension, the logs should be saved
| Priority: |
CurrentState: |
AppliesTo: |
Component: |
WaitingFor: |
| Enhancement |
Closed |
Engine |
Configure |
|
When an extension is installed, there is lots of nice information given on the webpage about what changed. It would be nice if everything was stored in a logfile for future reference. There are two ways to do this: store the raw actions in a text file, or save the result page as a static HTML page.
--
KipLubliner - 08 Apr 2011
See
EnhanceConfigureLogging
Probably needs to be done by recording the text output of the installation. Extensions can be installed from either the Web, or from the shell, so capturing results page as HTML wouldn't apply to the shell installation.
- Write a summary record to
working/logs/configure.log
- File format doesn't really support logging an install. Needs some discussion. Format is tabular, for example:
- Write the detailed report to
working/logs/configure/NameOfPackage-[action]-yyyymmdd-hhmmss.log
Not sure if this one needs a feature proposal. Probably does if any log file formats are changed. To make the log format more useful, add an Action column, Set, Install, Remove, Passwd, Set being the current format of Variable / Value? Proposed revised layout:
To late for 1.1.3, but this could probably make it into 1.1.4.
--
GeorgeClark - 09 Apr 2011
Committing the change to extension installation to log the results of the install. This needed some refactoring. The
Package::install method was renamed to
Package::_install and
Package::fullInstall renamed to
Package::install. The
uninstall method was modified to be consistent with
install, they now both run the pre and post (un)install routines and log all results.
--
GeorgeClark - 20 Jul 2011