[Octave-bug-tracker] [bug #58299] Local packages for different Octave versions cannot be installed in parallel

[Mike Miller]

Follow-up Comment #1, bug #58299 (project octave):

Putting aside the issue of modifying the m-files dynamically, can you please
test whether this works or doesn't work on Windows? It would be best if we can
start from a known baseline of what does work and what would be nice to
enhance.

On GNU/Linux, with the default configuration, the same set of local packages
can be installed and used with multiple Octave versions. M-files are installed
on top of each other in the same directory, so again, assume that's correct
for now. Oct files are installed in a directory that is named for the CPU, OS,
and Octave API version, so multiple sets of oct files can coexist. The local
package store is shared between versions, but that is not a bug, again
assuming the same set of packages.

There is definitely room for improvement, but please confirm first that you
can get the same current behavior on Windows so we characterize this
correctly.

I've offered this before elsewhere, but on my system I install packages in
$XDG_DATA_HOME/octave/$OCTAVE_VERSION_MAJOR/packages (e.g.
~/.local/share/octave/6/packages/...).

    _______________________________________________________

Reply to this item at:

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

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