[Octave-bug-tracker] [bug #51632] make global pkg paths always relative to OCTAVE_HOME, no need to pkg rebuild -global when path changes

[Philip Nienhuis]

Update of bug #51632 (project octave):

             Assigned to:                    None => philipnienhuis         
                 Release:                   4.2.1 => dev                    

    _______________________________________________________

Follow-up Comment #33:

Brought here from bug #57083 (where I got to learn some internals of pkg.m) by
a hint from Mike, and now that bug #57083 has been fixed, I think fixing the
original bug here is in principle going to be fairly easy to do for both local
and global packages.
It's actually along the lines that JWE sketched in comment #20.

It may be that paths relative to the various prefixes used by pkg.m work
better than paths relative to OCTAVE_HOME and that is going to be a little
more complicated as prefixes pop up at various places in pkg.m and its helper
functions. Some investigation is needed.

As to the original bug, "pkg rebuild" will have to be run *somewhere* because
AFAICS it's the only way an initial octave_packages file can be created. That
"somewhere" will obviously be "sometime" in the process of mxe-octave, i.e.,
before the fairly complete Octave installation in <mxe-octave>/dist/ is being
zipped or turned into an NSIS installer.

FTR, I think a fix can also be beneficial in some cases when running octave
from read-only locations. But maybe some extra steps are needed for making
docs available then.

I'll try to come up with a first provisional fix/cset and then we can see what
else can be / needs to be done for the wishes in later comments.

Release -> dev

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/