On Sun, Aug 10, 2008 at 8:00 PM, Benjamin Lindner <[EMAIL PROTECTED]> wrote: > A good question, It was just my first approach to do it. > Building packages not from within octave would fit into the whole building > process - just like dependencies, gnuplot, etc. > And I thought it would make the configuration of the .nsi installer easier, > if I have separate target directories for each package, by specifying a > manual --prefix. > > I may be misthinking here, though. If you do it by "pkg install ..." for > your .nsi installer, then I'll take a look into your nsi configuration > script.
I don't use "pkg install..." in the nsi script. I use it locally to create an image of the complete octave installation, which is then wrapped into an installer using a nsi script. This nsi script then just install the pre-compiled forge packages into their respective relative location (libexec/octave/packages/<name> and share/octave/packages/<name>). At the end of the installation process, I just do a "pkg rebuild" to recreate the package database with the correct paths. Michael. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
