Octave Transition

[Michael Dickens]

On Mon, Nov 18, 2013, at 02:24 PM, Ryan Schmidt wrote:
> I’m not sure I’d recommend adding a new octave-next port. That naming is
> nonstandard. Instead, can’t we just wait awhile, then update octave-devel
> to 3.7.x?

I have a ticket < https://trac.macports.org/ticket/41155 > suggesting
the transition to octave 3.8, which will be the next stable release;
ignore their attached Portfile, since it isn't what we want to be using.
 Octave "unstable" is currently at 3.7.7, which was not difficult to add
to octave-devel as a subport, with most of the same options as
octave-devel uses; in my testing, it performs quite well. I'm guessing
that 3.8 will have a few more API changes away from 3.6, just as 3.6 did
from 3.4, and so forth.  So, for folks on the "bleeding edge", I think
it's nice to have a port that supports their habit/wants.  The "next"
addition is what we use in GNU Radio-land, so I was just replicating
that here, temporarily to get that port in place.  Once 3.8 (or, maybe
3.8.1) is out, we can easily transition it back to octave-devel; or,
whatever we want. - MLD