On Wed, Mar 7, 2018 at 4:18 PM, Olaf Till <address@hidden> wrote:
Hi Doug,
you seem to have done much work to bring the control package to its
release state now. But do you really want to support Octave versions
down to 3.0.0? I had bumped it from originally >3.8.0 to >4.0.0 to
make our life easier with the linked code, >3.0.0 would be more
versions than before, and probably too difficult to handle...
Once we have agreed on the supported Octave versions, would you like
me to produce a release tarball?
Olaf
I made a mistake, you are correct >4.0.0 is the minimum way to go but...
I have tried it on 4.0.1-rc4 ( which i have on an old machine) and it installs but fails a lot of tests,
so we should go to >4.1.0
Test on 4.2.0 all pass
Test on stable all pass.
Test on default some fails that I am looking into. they segfault octave when calling fortran code.
I think it is a pointer size problem but not sure yet.
So if you fix this and a new release data then I would suggest that you do a release now.
There will always be more things to fix and there is time before default gets released.
thanks for your help.
doug
--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net