This version fixes a few bugs (some unfortunately introduced in the
This version will be labelled the "testing" (or recommended) version
of Octave on the download page of the Octave web site.
The snapshot is tagged in the usual way (ss-2-1-69) in the CVS
archive. It is also on the ss-2-1-63-patches branch so we can check
out that branch and apply any patches for any future bug-fix-only
snapshot if that is needed.
As always, if your favorite bug is still not fixed, please report it.
I'm working on making RPM packages of umfpack and glpk. I don't really
use LP or sparse stuff myself, so I was wondering if anyone can suggest
some tests to help me verify that octave 2.9.1 is linking to the new
libraries and they are working properly.
| I'm working on making RPM packages of umfpack and glpk. I don't really
| use LP or sparse stuff myself, so I was wondering if anyone can suggest
| some tests to help me verify that octave 2.9.1 is linking to the new
| libraries and they are working properly.
For glpk, look at the two test scripts in the scripts/optimization
directory (not .m because I did not want them to be installed with the
other .m files).
For the sparse code, see the attached file. You'll need the test code
from octave-forge to run the tests. I think splu uses umfpack.
## THIS IS AN AUTOMATICALLY GENERATED FILE --- DO NOT EDIT ---
## instead modify buildtests.sh to generate the tests that you want.
## run preset sparse tests. All should pass.
function [passes,tests] = sptest
disp('writing test output to sptest.log');