Octave-Forge: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Carandraug (talk | contribs) (/installing packages/ mention the system package manager. Also -forge option is now more common than download file manually) |
No edit summary |
||
| Line 1: | Line 1: | ||
Octave-Forge (http://octave.sf.net) is a community project for collaborative development of GNU 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) should go in the [[Tips and tricks]] page. | Octave-Forge (http://octave.sf.net) is a community project for collaborative development of GNU 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) should go in the [[Tips and tricks]] page. | ||
GNU Octave also needs the equivalent of CPAN so that packages such as epstk which have been developed elsewhere can be archived. [http://agora. | GNU Octave also needs the equivalent of CPAN so that packages such as epstk which have been developed elsewhere can be archived. [http://agora.octave.org Agora Octave] is a fledgeling proposal to do that (talk to [[User:JordiGH|JordiGH]] about it). 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. | ||
== Installing packages == | == Installing packages == | ||