Modified Portfile for Octave 3.5.90 attached

Nicolas Pavillon pavillon.nicolas at
Sun Dec 18 08:05:22 PST 2011


If that is the path taken, I could take care of upgrade most of the octave-foo packages, as I had started a PortGroup for more recent octave packages, and thus have most of the work done already.



> I'd suggest making an octave32 port copied from the current octave and
> updating octave to 3.4, leaving octave-devel as the latest development
> version as is the intent for -devel ports in general. Then make all
> octave-FOO replaced_by octave32-foo.
> If in future some of the packages are updated to work with 3.4, their
> portfiles can just be updated and the replaced_by removed.
> - Josh
> _______________________________________________
> macports-dev mailing list
> macports-dev at

More information about the macports-dev mailing list