[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):

                  Status:               Confirmed => Patch Submitted        

    _______________________________________________________

Follow-up Comment #34:

Here's a first cset, aimed at replacing OCTAVE_HOME in the paths in the global
octave-packages file.
It works mostly fine, but it's perhaps it's presently more a
proof-of-concept.

It has been tested on Windows and Linux.
In Windows I ran Octave directly from the <mxe-octave>/dist/octave...
installation, being able to use all prebuilt package still residing on the
(read-only mounted) linux partition. To do that I simply copied the
octave-packages file from Windows over to
<mxe-octave>/dist/octave/mingw64/share/octave/ (did that in Linux where I can
mount the Windows drive read-only) and back in Windows made a shortcut to the
octave.vbs file in said mxe-octave installation tree.

So I think that proves that the global octave_packages is now relocatable.

I saw one glitch:
While trying to install the econometrics-1.1.2 package on Windows I ran into
error messages about doc building. IIRC ?gen_lookfor_cache? or so? still used
the 8.3 style paths and complained about some path or file not found - sorry I
didn't save the messages (was late at night :-) )
In the end the search path contained entries for (IIRC)
.../econometrics-1.1.2/doc and econometrics-1.1.2/packinfo
IIRC restarting Octave and a "pkg rebuild" solved it.

Comments welcome.

(file #47765)
    _______________________________________________________

Additional Item Attachment:

File name: bug_51632_first_fix_global_OCTAVE_HOME.cset Size:7 KB
   
<https://savannah.gnu.org/file/bug_51632_first_fix_global_OCTAVE_HOME.cset?file_id=47765>



    _______________________________________________________

Reply to this item at:

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

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