Hello Benjamin To my experience, recently imported forge-packages by Xavier are not easy to install by the user level because they have a lot of external depencies. And also, it is difficult to install symbolic packages that uses ginac and cln libralies and pkg-config command that does not inculed in mingw or msys. You have to get it from Gimp tool kit.
I think that it is not always necesarry to pre-build octave-forge packages to your packages. However you have to check them and gives users enough information of dependencies. And there are packages like engine uses the unixy pipe code that is not easy to build under the mingw. You also indicate which packages cannot be installed by pkg install command. Regards Tatsuro --- Benjamin Lindner <[EMAIL PROTECTED]> wrote: > > > > > > Great, then I'd love to see it. If its ready for prime time we need to > > think about the structure of the source-forge FRS for the new MinGW package > > . The easiest would be is if like Michael you include all of the > > octave-forge packages and then we remove the additional Windows packages > > sub-project, rename the existing Windows sub-project to MSVC Windows and > > create a new sub-project for MinGW Windows for you to upload to. > > I see that Michael set a high refence level with his installer :) > The version I have now is not (yet) so complex. > I have a package that contains Octave, an Editor, Gnuplot and mingw's > gcc along with a core msys envionment. Ah yes, and ATLAS libraries for > some architectures and the installer detecting the appropriate versino > at install-time. > > The supplied gcc and msys enable the user to install octave-forge > packages using the "pkg install package-1.0.0.tar.gz" mechanism. > > It does not contain pre-compiled octave-forge packages. > To be frank - I had not planned to include them (yet). > The idea was that shipping octave with gcc&msys would not require to > include compiled forge-packages in the installer - this would save me > some work :) > > Michael's pre-compiled octave-forge packages in the sub-project would I > guess most probably not work with the mingw32-release of octave anyway, > so the mingw32 release and these packages have no dependency. > > > > If you don't think its ready for prime time I can host it on my personal > > machine as previously for testing purposes. > > Well you made me reconsider if my installer is really yet 'prime time'. > I would have said yes, but as I said, it does not include forge-packages . > > So what is the general opinion? > Is a mingw-binary without pre-compiled forge-packages of any interest at > all? > > If not, well then I'll dig into it and do my best to pack them into the > installer, and come back when ready. > > regards > 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 > -------------------------------------- Stop! Global Warming ~ Yahoo! JAPAN Earth Project http://pr.mail.yahoo.co.jp/earthproject/ ------------------------------------------------------------------------- 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
