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

[Nicholas Jankowski]

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

rmdir - that would maybe work in the short term.  I do see that @jwe already
pushed a possible rmdir fix to stable on that bug report.  So I can give that
a try on windows after the next 6.2.1 buildbot cycle. 

Took me a while to sort out what 'prefix' meant too and how that worked into
things. I'm still not sure what archprefix is. 

my understanding of 'prefix' is just from the help:


          pkg prefix ~/my_octave_packages

          sets the installation prefix to '~/my_octave_packages'.
          Packages will be installed in this directory.

          It is possible to get the current installation prefix by
          requesting an output argument.  For example:

               pfx = pkg ("prefix")


e.g., whatever the prefix is, that's "where things will be installed now
unless you tell pkg otherwise".  looking at default_prefix, it sets local to
be in the users profile folder (~ on *nix systems,  C:\users\*username* on
windows) and global to be inside the Octave installation.

it appears that that -global and -local switches essentially just make a
prefix switch.  I "think" these changes are meant to be temporary, and they
aren't.  I never paid attention to this before, since on windows before v6
everything defaulted to global. I may install v5 or v4 copy of octave and
compare the pkg behavior to see if this is new.

    _______________________________________________________

Reply to this item at:

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

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