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

[Philip Nienhuis]

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

Maybe we are so focused on fixing problems by patching function code in Octave
that we don't see the obvious...

As also suggested in comment #5, why can't we simply add code along the lines
of the suggestion in comment #5 in the site-wide .octaverc? or alternatively
in the version-dependent global .octaverc?

For newer Octave versions the problem will be solved automatically that way.
IMO a big benefit would be that no changes for pkg.m are needed then as all
required functionality has already been implemented there; all we need to do
is invoke it.
If we're quick we can even do it for upcoming 6.1.

We'd need to agree on a good path, e.g.,
~/octave/<full_release>/
-or-
~/octave/<major_version>/  ## ~ cf. Mike comment #3
-or-
~/octave/local_packages/<major_version>/  ## a variant
-or-
~/<whatever>

We can enter any code in that site-wide or global .octaverc, e.g. the code in
comment #5, or adapted paths, or even:

if (ispc)
  <set local package store somewhere in %APPDATA%/Roaming/...>
else
  <set local store in dedicated Linux or Mac way>
endif



    _______________________________________________________

Reply to this item at:

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

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