[Octave-bug-tracker] [bug #60472] pkg -global option changes pkg prefix for subsequent calls

[Nicholas Jankowski]

Follow-up Comment #7, bug #60472 (project octave):

jumped back to older versions of pkg, and the persistent prefix change
behavior appears to be persistent as far back as v4.4.1 (checked 5.1.0 as
well).  the rmdir crash seems new, though.

(following is the same in v4.4.1 ad 5.1.0)

>> rmdir("")
ans = 0

>> pkg prefix
Installation prefix:            
C:\Programs\Octave\OCTAVE~1.1-W\share\octave\packages
Architecture dependent prefix:  
C:\Programs\Octave\OCTAVE~1.1-W\lib\octave\packages

>> pkg install -local abc
error: pkg: failed to read package 'abc': Couldn't resolve host name
error: called from
    pkg at line 429 column 17

>> pkg prefix
Installation prefix:             C:\Users\NICHOL~1.JAN\octave
Architecture dependent prefix:   C:\Users\NICHOL~1.JAN\octave

>> pkg list tsa
Package Name  | Version | Installation directory
--------------+---------+-----------------------
         tsa  |   4.4.5 |
...\Octave\OCTAVE~2.0-W\mingw64\share\octave\packages\tsa-4.4.5

>> pkg uninstall tsa

>> pkg install -forge tsa
For information about changes from previous versions of the tsa package, run
'news tsa'.

>> pkg list tsa
Package Name  | Version | Installation directory
--------------+---------+-----------------------
         tsa  |   4.6.2 | C:\Users\NICHOL~1.JAN\octave\tsa-4.6.2



running a pkg rebuild without changing the prefix back, pkg list only shows
tsa, and only that package will load, even though 'pkg local_list' and
global_list point to the right files and they are properly populated, but
there is no local .octave_packages file. forcing -global again, and a pkg
rebuild, shows all but tsa and still refuses to build a local
.octave_packages.

at this point, I'm not sure what's going on.  right now the general rule of
thumb for this windows setup is: never call install/uninstall without manually
specifying -local -global.  never call update.  


    _______________________________________________________

Reply to this item at:

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

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