[MacPorts] #41155: Preparing for new Octave release

[MacPorts]

#41155: Preparing for new Octave release
----------------------------+--------------------------------
  Reporter:  kingcrimson@…  |      Owner:  macports-tickets@…
      Type:  update         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.2.1
Resolution:                 |   Keywords:
      Port:  octave         |
----------------------------+--------------------------------

Comment (by michaelld@…):

 OK; interesting stuff. What I'm going to do sometime today or tomorrow --
 I'm very close; everything works on 10.8 under GCC or Clang; I'm testing
 on 10.9 today with just Clang -- is update octave, octave-devel, and all
 of the octave-* ports.  octave will replace octave-devel, and there will
 be only the 3.6 release of octave for a while. After a suitable amount of
 time, say, 2 months, I'll reinstate octave-devel to be the 3.8 release,
 after verifying/fixing the octave-* ports work with it.

 "Why?" you ask ...

 Most octave users are using octave-devel because it works; the current
 octave port (3.2.4_16) does not work for everyone, and especially folks
 using 10.7+; many/most folks have moved to octave-devel because they had
 no choice if they wanted octave, rather than because they wanted the
 latest octave. Because the 3.6 release is very stable, it makes sense to
 move it to octave; but, instead of putting the imminent 3.8 release as
 octave-devel right now -- which folks using the current octave-devel would
 be upgraded to if this were done immediately -- we set octave-devel as
 "replaced by" octave for a short time to get folks transitioned to using
 the octave port. Then after that short time I reinstate octave-devel --
 there will always be hold-outs who do not update, but those will be many
 fewer than if I did the upgrade right now.

 So, when we get a few months down the road I will figure out what makes
 sense for the Portfile to add the 3.8 release back in. Hopefully some of
 the stdlib issues will be fully resolved by then, as will some with
 GhostScript and other ports upon which octave depends.

 BTW> Related: whatever happened to using itsol?  I thought octave 3.8 was
 going to be using that port ...

-- 
Ticket URL: <https://trac.macports.org/ticket/41155#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X