According to < http://octave.sourceforge.net/communications/index.html >, this octave package does not auto-load. I'm not sure how one makes a package auto-load yet. With the forthcoming release of octave 3.8.0 (right now 3.7.7, sort of a devel or beta level), I'm working on fixing the octave ports including octave-communications. It will be easier for everyone if we have "octave" be the 3.6 stable release, and "octave-devel" be the 3.7+ release -- some packages do not work yet with 3.7.7+, but they will work with 3.6. This effort has been long-overdue :) - MLD
On Tue, Nov 12, 2013, at 12:04 PM, Marius Schamschula wrote: > What does > > octave> path > > give you? > > You should have > > /opt/local/share/octave/packages/communications-1.1.1 > > listed. > > If not you can manually add the path using > > octave> addpath('/opt/local/share/octave/packages/communications-1.1.1') > > Unfortunately, I'm not an expert in the internal machinery of building > octave-forge packages under MacPorts. Maybe someone else can explain why > the path was not automatically added. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users