From maintainers-request at octave dot org Sat Jun 18 04:51:47 2005 Subject: Re: packaging system From: =?ISO-8859-1?Q?S=F8ren_Hauberg?= To: Stefan van der Walt CC: "John W. Eaton" , maintainers@octave.org Date: Sat, 18 Jun 2005 11:51:09 +0200 I'm going to need a little hand-holding here, as don't quite understand your post. You want the installation routine to (before installation) check if a file called pre-install.m exist, and if it does run it from Octave, right? If so then that's just a minor change that can be done in a minute. You also want a similar post-install.m, to be executed at the end of installation? (btw, should these be .m files or shell scripts?) What I don't get is what these scripts should do. Could you elaborate a bit? /Søren Stefan van der Walt wrote: > 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 >> > >