Contributing to the development of packages/modules: Difference between revisions

No edit summary
(→‎Checking out the svn: hg instructions)
Line 11: Line 11:
Once you have fixed the bug, you can send a patch with your changes. How do you this? Check the [http://octave.sourceforge.net/developers.html developers help] page.
Once you have fixed the bug, you can send a patch with your changes. How do you this? Check the [http://octave.sourceforge.net/developers.html developers help] page.


=== Checking out the svn ===
=== Checking out the package source ===
You can also checkout the package in question using svn. For example if you wan to checkout the general package you would run
You can also checkout the package in question using svn. For example if you want to checkout the <tt>general</tt> package you would run


<pre>svn co https://octave.svn.sourceforge.net/svnroot/octave/trunk/octave-forge/main general general_to_debug</pre>
<pre>svn co https://octave.svn.sourceforge.net/svnroot/octave/trunk/octave-forge/main general general_to_debug</pre>
Line 18: Line 18:
This will create a folder <code>general_to_debug</code> in your current directory. You can hack away as much as you can and then produce the
This will create a folder <code>general_to_debug</code> in your current directory. You can hack away as much as you can and then produce the
patch and send it to the mailing list.
patch and send it to the mailing list.
Many of the packages now use Mercurial (hg) repositories for version control. To checkout, for example, <tt>odepkg</tt>:
<pre>hg clone http://hg.code.sf.net/p/octave/odepkg odepkg_to_debug</pre>


=== Contributing new file or bundle of files ===
=== Contributing new file or bundle of files ===
281

edits