Michael Goffioul wrote: > On Sat, Aug 9, 2008 at 9:57 PM, Benjamin Lindner <[EMAIL PROTECTED]> wrote: >> Giving Micheals statements some thought, I agree that bundling forge >> packages is the way to go. Nevertheless the dependencies can (and probably) >> should be included, in case you want to, say, update a forge package. >> I have to look into building forge packages offline (i.e. not from within >> octave using "pkg install ...") > > Just a question: > why would you want to build forge packages outside octave (not using > pkg)? When generating binary installers, I still forge packages through > octave. > > Michael. >
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. benjamin ------------------------------------------------------------------------- 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
