[Octave-bug-tracker] [bug #59821] [octave forge] (ga) pkg update with ga 0.10.2 installs in user home folder instead of packages folder on windows

[Nicholas Jankowski]

Follow-up Comment #8, bug #59821 (project octave):

yes, this is the first I recall seeing it. Saw some comments on pkg in News
but didn't see anything about changing that aspect of pkg behavior.  

Just to clarify, if we're now going to have cross-platform consistent  
package handling- 

(1) i didn't think the 'pkg update' command took other flags.  but -global
seemed to do something.  do all of the 'install' options pass through to
'update' as well? if so that would be a useful and easy doc note to add.  

(2) can you explain why I still have a local ga&nan, an older global ga&nan,
and after 'pkg update -global' and 'pkg rebuild' I'm now seeing just the old
versions in pk list, showing the global location? did something about that
command tell octave to ignore the presence of things in local? and if so why
didn't it actually update the global packages? may be some kindof bug hiding
in there.

(3) If I still want to operate with packages being isolated to the installs
like they were pre-v6, should 'pkg update -global' work or should 'pkg update'
just be avoided altogether? 

    _______________________________________________________

Reply to this item at:

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

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