>> pkj list
PackageName | Version | Place | InstallationDir
------------+----------------+--------+-----------------------------------------------------------------------------
control | 3.2.0 | user | ~/octave/control-3.2.0
signal | 1.4.1 | custom | ~/Library/Application Support/Octave.app/4.4.1/pkg/signal-1.4.1
tablicious | 0.1.0-SNAPSHOT | custom | ~/Library/Application Support/Octave.app/4.4.1/pkg/tablicious-0.1.0-SNAPSHOT
Non-installed packages on Octave load path:
Name | Version | Dir | RepoStatus
------------+---------+----------------------------------+-----------
packajoozle | 0.0.0+ | ~/local/repos/octave-packajoozle |
>> pkj uninstall control
pkj: uninstalling from custom:
pkj: packages uninstalled OK
>>
That ain't right. It doesn't exist in custom, and the uninstallation didn't happen.
When I did this, there was previously a control installed in custom, and doing pkj uninstall control uninstalled that.
After a restart, same thing:
>> pkj uninstall control
pkj: uninstalling from custom:
pkj: packages uninstalled OK
>>
Also raises the question of what pkj uninstall <foo> should do when there is a <foo> installed in multiple Places, or when there are multiple versions of <foo> installed. I think maybe it should uninstall all of them, instead of finding and uninstalling just one.
That ain't right. It doesn't exist in
custom
, and the uninstallation didn't happen.When I did this, there was previously a
control
installed incustom
, and doingpkj uninstall control
uninstalled that.After a restart, same thing:
Also raises the question of what
pkj uninstall <foo>
should do when there is a<foo>
installed in multiple Places, or when there are multiple versions of<foo>
installed. I think maybe it should uninstall all of them, instead of finding and uninstalling just one.