[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 #23, bug #51632 (project octave):

re: comment #20:  that was my original thought, as I was messing with in
comment #7 and comment #9. I had hoped that pkg would process the strings and
expand out OCTAVE_HOME(), so that the only thing to do was store all the
bundled packages with either relative path names or names relative to
OCTAVE_HOME.  then no pkg rebuild would be required for either zip or exe.
However, it appears I was mislead by how pkg displays the path and actually
stores and uses the path, and haven't looked at it further.

re: comment #21: many people consider the zip versions of programs to be
'portable' versions. run from flash drive, etc. Octave zip is not actually a
portable version since it relies on absolute paths and makes use of the user
folder. Having everything able to work relative to OCTAVE_HOME, which the zip
version successfully finds on startup, would be step 1 to making it actually
portable in addition to solving the pkg rebuild issue. I guess 'relative to
octave_home' is still an absolute path in a sense, depending on where the full
path expansion occurs.

getting sidetracked into how to 'auto rebuild' as per comments #10-18 I
stopped short of diving into pkg to see where it gets locked into absolute
paths. First thought would be to see if there are places you could parse and
'eval' the string, but I know some people dislike eval in general. 

jwe: (re: comment #19 re: comment #6)  hah... brilliant ... let's just pretend
I never made that comment.

    _______________________________________________________

Reply to this item at:

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

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