|
| From: | Philip Nienhuis |
| Subject: | [Octave-bug-tracker] [bug #58225] Installing package fails when package was already installed globally |
| Date: | Sun, 3 May 2020 17:33:38 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0 Lightning/5.8.1 |
Follow-up Comment #10, bug #58225 (project octave):
For that matter even .m-file functions may not be compatible between Octave
releases.
But your suggestion of having the local package .oct files live in separate
subdirs for each Octave release is probably a good one IMO.
earlier on I've pondered a bit about this but I'm still a bit confused about
how a new Octave release with a new api version could see the local packages
already installed. I suppose a new Octave release would have to reinstall
local packages to be able to have new api-compatible .oct files.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58225>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |