I still think that something like a pre- and post-install script would
be useful. Why stop at being able to modify the installation prefix?
Why not create a standard structure with all installation variables,
populated before installation starts.
The installing package then has an opportunity to modify this struct
in the pre-install script after which installation takes place.
Afterwards, the post-install script can do any additional
admin/cleanup needed while having access to that information still.
Your package has everything in place to do this already. It would
just require some minor modifications.
Regards
Stefan
On Fri, Jun 17, 2005 at 11:01:35PM +0200, S?ren Hauberg wrote:
Hi
I've updated the code (it's still at http://hauberg.org/octave-package),
with the following changes:
*) If the archive contains a directory, cd to that directory. This means
that package can keep it's files in a directory (e.g. PACKAGE-VERSION).
*) A bit more error checking. Not enough though
*) Support for uninstallation of packages. No dependency checking is
done during uninstallation.
*) The installation prefix is defined by the global variable
OCTAVE_PACKAGE_PREFIX. If this variable is not defined an error is
issued. Packages will be install in OCTAVE_VALUE_PREFIX/PACKAGE-VERSION
As long as the packages doesn't have to many errors the code is usable
in it's current state.
/Søren