|
| From: | Markus Mützel |
| Subject: | [Octave-bug-tracker] [bug #58299] Local packages for different Octave versions cannot be installed in parallel |
| Date: | Mon, 4 May 2020 16:46:20 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0 |
Follow-up Comment #2, bug #58299 (project octave):
I tried by installing the "windows" package locally with the following command
in Octave 5.2:
pkg install -local -forge windows
After this, the package is installed in C:\Users\Markus\octave\windows-1.4.0:
>> cd C:\Users\Markus\octave\windows-1.4.0
>> dir
. @octave_com_object iscom.m
packinfo x86_64-w64-mingw32-api-v53
.. doc-cache mat2xls.m
test
Then I closed Octave 5.2 and tried to install the package again using the same
command in a self-compiled Octave 6.0.1.
The installation succeeds. But all files from the previous installation are
gone. In particular the "x86_64-w64-mingw32-api-v53" with the binaries for
Octave 5.2 has disappeared:
>> cd C:\Users\Markus\octave\windows-1.4.0
>> dir
. .. @octave_com_object
doc-cache iscom.m mat2xls.m
packinfo test
x86_64-w64-mingw32-api-v54
This might lead to problems if a user wants to change between different Octave
versions frequently and has local packages.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58299>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |