[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]

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

@Markus:
Thanks for testing & pushing - I didn't expect it to happen that soon :-)

@JohnD:
My current trick is copying over from my Windows partition / installed Octave
by a rule in binary-dist-rules.mk
Today I upgraded my desktop box to Mageia 7, reinstalled all build tools and
when running a fresh mxe-octave clone I saw:

[check requirements]
/bin/bash: octave: command not found
Warning - could not find native build version 6.0.0 of octave - some packages
may fail, but continuing
:


....so the mxe-octave build tools are already prepared to invoke Octave on
Linux in some way.
As most devs simply need a Linux build tree for Octave in the first place (to
create the dist archive needed for mxe-octave) I figure a simple rule in
Makefile.in could do the trick.

The octave_packages file is simply a text .mat file, ideally written by Octave
itself.
One doesn't even need a current Octave when cross-building dev Octave; if one
adds <mxe-octave>/.../mingw64/share/octave/6.0.0/m/pkg to the path the
installed Octave (on Linux) will use the most recent scripts.
"pkg rebuild" is a pretty straightforward function that merely scans the
package install directory (m-files) and adds the found package directories +
related lib/octave/<arch>/ package directories + other info to the packages
cellstruct. It doesn't run any of the functions so this is fairly safe.



    _______________________________________________________

Reply to this item at:

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

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