[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #58299] Local packages for different Octave ve
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #58299] Local packages for different Octave versions cannot be installed in parallel |
Date: |
Mon, 4 May 2020 17:42:53 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.129 Safari/537.36 |
Update of bug #58299 (project octave):
Severity: 3 - Normal => 1 - Wish
Priority: 5 - Normal => 3 - Low
Item Group: Unexpected Error => Feature Request
Status: None => Confirmed
_______________________________________________________
Follow-up Comment #3:
Ok, confirmed. I've found that by deleting the package cache file, Octave
doesn't know about the other versions of the package oct files and won't
delete them, but then fails when it tries to extract doc strings from the
incompatible oct files. Added that fact to bug #57826.
So yes, I think we're on the same page on all operating systems, and I agree
it would be a good enhancement to install packages by default in a
per-Octave-version directory in the user's home / profile directory. I think
it's an enhancement because most users don't regularly use multiple versions
of Octave at the same time, and normally need to reinstall all packages when
updating to a new version anyway.
IMHO, that directory should be based on the major version of Octave, so
packages installed in version 7.1.0 are still found and work in version 7.3.0.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58299>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/