5
edits
Release History: Difference between revisions
add a comma and move a word, to make the sentence easier to read
(More 2.0.x release dates from the ftp archive.) |
Waldyrious (talk | contribs) (add a comma and move a word, to make the sentence easier to read) |
||
| Line 1: | Line 1: | ||
Reverse chronological list of Octave releases. | Reverse chronological list of Octave releases. | ||
All recent released versions going back to version 3.4.0 are tagged in the [http://hg.savannah.gnu.org/hgweb/octave hg archive] with a tag of the form release-MAJOR-MINOR-PATCH. So version 4.2.1 is tagged with "release-4-2-1". However, note that trying to build from an old tarball release isn't exactly the same thing as updating the hg archive to the corresponding hd id and trying to build from that. There are a number of generated files that are included in the tarball releases that are not stored in the hg archvie. For old releases, using current tools to generate those files will likely result in some differences unless you have the same old versions of tools like autoconf, bison, flex, gperf, etc. | All recent released versions going back to version 3.4.0 are tagged in the [http://hg.savannah.gnu.org/hgweb/octave hg archive] with a tag of the form release-MAJOR-MINOR-PATCH. So version 4.2.1 is tagged with "release-4-2-1". However, note that trying to build from an old tarball release isn't exactly the same thing as updating the hg archive to the corresponding hd id and trying to build from that. There are a number of generated files that are included in the tarball releases that are not stored in the hg archvie. For old releases, using current tools to generate those files will likely result in some differences, unless you have installed the same old versions of tools like autoconf, bison, flex, gperf, etc. that were used to generate the old tarball release. | ||
{| | {| | ||
|- | |- | ||