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

[Philip Nienhuis]

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

@Markus: see bug #36477, bug #40444, bug #57463 and bug #55822

To be precise in bug #58225 I referred to .m files in OF packages, and it's
not those .m-files that differ between Octave versions but rather many OF
packages have .m files that explicitly depend on some range of Octave
versions. (sorry for nitpicking)
FWIW my experience is that .m-files usually have a much longer lifetime across
Octave releases than .oct files. Other than that I think Mike's suggestion is
a good one.

But maybe the mxe-octave installer should be adapted to wipe local package
directories relating to its Octave version (after user consent, of course).

This bug report is about locally installed packages but for global packages I
see a lot of similarities.
On Windows all global stores are installed separately for mxe-octave
cross-builds so little problems there. But AIU on *nix the global package
stores (both in share/ and lib/) are shared between Octave versions. Will
e.g., updating or reinstalling a global package running a newer Octave version
(with different api no.) lead to removal of the existing subdir with .oct
files for the older api? (I guess so, looking at the logic in pkg.m)


    _______________________________________________________

Reply to this item at:

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

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