Hello, I had taken a quick look at the octave extension, and it seems that the main issue is that most of them were not updated, as the installation way changed, so that they were kept to old versions, still compatible with the installation way provided in octave-1.0 port group. For this reason, several of them are not compatible with octave 3.6, but there are newer versions which are meant for more recent versions of octave.
I had submitted a new version of the port group, which should work to install the newer extensions (https://trac.macports.org/ticket/31949). It is however meant only for the new installation way, so that older packages should be kept on version 1.0. Cheers, Nicolas >> >> I was asking since octave is pretty old compared to octave-devel and >> needed octave for a bit, but I don't have the cycles to do this myself. >> >> It does seem that if the addons don't work with octave-devel they should >> be deprecated. We could copy octave to octave32 and rename any octave-* >> that only with with 3.2.x. > > I think at least some of the addon ports are in the situation of not > being updated to the latest version because it's no longer compatible > with octave 3.2. The converse may also be true in some cases, with the > older version being incompatible with octave 3.6. > > - Josh > _______________________________________________ > macports-dev mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-dev _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
