octave2.9-forge does not set the load path properly

[Albert Cardona]

Binary package hint: octave2.9-forge

1) Install octave and octave-forge, version 2.9:

$ sudo apt-get install octave2.9 octave2.9-forge

2) launch octave:

$ octave
ostave:1>

3) try to use a function from octave-forge, such as "specgram":

octave:1> specgram
error: `specgram' undefined near line 1 column 1

4) Easy solution: add the load path for the signals package:

octave:1> addpath ("/usr/share/octave/site/api-v22/m/octave2.9-forge/signal/")
octave:2>

Now it works ... the function 'path' lists all the paths to the octave package, but NOT even one to the directories where the octave-forge packages exist.
It's puzzling, and I'd say it's a bug. In Previous installments of these packages (back in feisty), the octave-forge was correctly setting the load path.

My system: ubuntu 7.10 dist-upgraded to today 2008-03-09.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.