182
edits
ArunGiridhar (talk | contribs) Tags: Mobile edit Mobile web edit |
ArunGiridhar (talk | contribs) Tags: Mobile edit Mobile web edit |
||
Line 8: | Line 8: | ||
* Initial clone: <pre>hg clone https://hg.savannah.gnu.org/hgweb/octave/</pre> | * Initial clone: <pre>hg clone https://hg.savannah.gnu.org/hgweb/octave/</pre> | ||
You can then bootstrap, configure and make, maybe make install. | You can then bootstrap, configure and make, make check, maybe make install. | ||
* To update on a regular basis, you can do <pre>hg pull -u</pre> or <pre>hg pull && hg up</pre> | * To update on a regular basis, you can do <pre>hg pull -u</pre> or <pre>hg pull && hg up</pre> | ||
* To make a '' | * To make a ''local clone'', you can clone from your main Octave repository on your computer to another directory like this: <pre>hg clone octave myfeature</pre> which will clone the Octave directory into a new directory called "myfeature". You'll need to cd to the correct directory first. Then you can cd into the new directory and run bootstrap, configure, make. To prevent a fresh download of gnulib, you can specify the path to the first Octave directory's gnulib if you want. | ||
It is best practice to make a new clone directory for each feature or bugfix you work on, which makes recovery from mistakes much easier. | It is best practice to make a new clone directory for each feature or bugfix you work on, which makes recovery from mistakes much easier. |
edits