[Octave-bug-tracker] [bug #51632] MS Windows portable (i.e. zip) version cannot find pre-installed packages, needs pkg rebuild, not mentioned at first run

[Nicholas Jankowski]

Follow-up Comment #7, bug #51632 (project octave):

interesting find:  octave_packages DOES work if you put a fullfile() function
in for path.

replacing 

C:\Octave\OCTAVE~1.1\lib\octave\packages\signal-1.3.2 

with 

fullfile(OCTAVE_HOME (), "\share\octave\packages\signal-1.3.2")

allows pkg list to read octave_packages.  however, it doesn't quite  work
perfectly.  


>> pkg list signal
Package Name  | Version | Installation directory
--------------+---------+-----------------------
      signal  |   1.3.2 | ...\share\octave\packages\signal


not sure why it's truncating the -1.3.2 from the path. 

fixing that, this should be a straightforward way to have the portable one
find the packages right away taking advantage of the  environment variables
set on octave startup to avoid needing to hardcode package links. 

honestly, this would be an interesting way to store the global package paths
anyway if we wanted to make a truly portable octave version.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51632>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/