Octave 3.4.0 is released

[stephen@…]

IMO, this patch is more appropriate here. See also ticket #28351 (same title, for 'octave' port).

The patch is trivial, but untested by me yet. Apparently it works for somebody (see #28351 :-).

[ryandesign@…]

Why file this as a new ticket? Doesn't #28351 already completely cover the request to update octave?

[michaelld@…]

I think the question is which port to upgrade to 3.4.0: 'octave' (ticket #28351) or 'octave-devel' (this ticket). I'm inclined to do the latter, since 'octave' (at 3.2.4r4) is stable and has users -- I presume some of whom would be displaced by updating to 3.4 (due to the usual incompatibilities involved in such version changes, not that I know of any). 'octave-devel' (at 3.3.91r2) was just a beta for the new 3.4 series anyway, and hence IMHO is the correct port to upgrade. If we agree on this, then let's close the other ticket & I'll do the upgrade; otherwise, close this ticket & have Andre upgrade that port.

[stephen@…]

Uh, shouldn't you tell me what #28351 covers? From where I stand, there are two separate ports, whose Portfiles have diverged and whose apparent maintainers differ in levels of activity. This is the minimum-distance port for the proposed update, both in size of diff and probable time-to-release.

The build succeeded for me on "mature" hardware/OS, while octave does not (separate ticket filed):

port 1.9.99
Mac OS X 10.5.8 "Leopard"
MacBook Pro Intel Core 2 Duo @2.4GHz, 2GB RAM

[michaelld@…]

Except the initial question, I agree with what you wrote. As you say, the patch is meant for octave-devel and it's a trivial change. That said, MacPorts folks (including Andre) might decide that the 3.4 series is stable enough for us to move the upgrade to 'octave', and then change 'octave-devel' to some 3.4.1+ beta release (as available). Please give us a day or 2 to figure out which way to proceed.

[ryandesign@…]

#28351 was the request to update octave to the latest stable version 3.4.0, which IMHO makes this ticket a duplicate of that one. The diff was expressed against octave-devel since that is what it was based on, but octave-devel is a -devel port -- by definition supposed to be for the latest development version, while octave is a stable port -- supposed to be for the latest stable version.

Andre does not have time to maintain his ports anymore so octave is now nomaintainer (r78753) and others may feel free to step in; perhaps Michael would like to take charge since he already has octave-devel.

[michaelld@…]

OK; I didn't know about Andre's status, so I'll deal with these tickets. I, also, don't have time to investigate 'octave' issues; I'm happy to deal with 'octave-devel' since I'm there already, but really cannot add to my load at this time.

[michaelld@…]

IMHO, Octave version 3.4.0 isn't "stable" yet in the same way that version 3.2.4 is. Thus, unless someone truly protests, I'm going to upgrade the port 'octave-devel' to 3.4.0 and leave the port 'octave' alone. That way, current Octave users can continue using what they have, and those wanting to test out the latest can continues to use that.

[ryandesign@…]

Sounds good to me. Thanks.

[michaelld@…]

Per ticket #29517, r78773, I've updated octave-devel to 3.4.0, and I'm leaving octave alone.