Octave-Forge: Difference between revisions
(Port from old wiki) |
No edit summary |
||
| Line 4: | Line 4: | ||
Octave also needs the equivalent of CPAN so that packages such as epstk which have been developed elsewhere can be archived. Before that is possible we need a packaging system which works for both octave and matlab (and maybe scilab if you are feeling ambitious) without too much work on the either the developers or the users end, even for users working in a tool desert such as Windows. Feel free to expand on the definition of such a system on this page. | Octave also needs the equivalent of CPAN so that packages such as epstk which have been developed elsewhere can be archived. Before that is possible we need a packaging system which works for both octave and matlab (and maybe scilab if you are feeling ambitious) without too much work on the either the developers or the users end, even for users working in a tool desert such as Windows. Feel free to expand on the definition of such a system on this page. | ||
[[Category:OctaveForge]] | |||
Revision as of 22:04, 22 November 2011
Octave-Forge (http://octave.sf.net) is a community project for collaborative development of octave extensions. If you have a large package that you want to open up to collaborative development, or a couple of m-files that you want to contribute to an existing package, octave-forge is the place to do it.
Tiny helper functions (the equivalent of e.g., shell aliases) which aren't needed for compatibility purposes should live in a utility page on this wiki.
Octave also needs the equivalent of CPAN so that packages such as epstk which have been developed elsewhere can be archived. Before that is possible we need a packaging system which works for both octave and matlab (and maybe scilab if you are feeling ambitious) without too much work on the either the developers or the users end, even for users working in a tool desert such as Windows. Feel free to expand on the definition of such a system on this page.