[Octave-bug-tracker] [bug #59821] "pkg update" on windows unexpectedly installs packages to local

[Markus Mützel]

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

IIRC, the criterium of whether an installation will by default be global or
local is *not* whether there is *write-access* to the global store. Instead,
the criterium is whether Octave runs as root (superuser) on Linux or with
elevated privileges (i.e. administrator rights) on Windows.
Maybe that could be clearer in the documentation.

I'm not sure if there is convenient wording that could be used cross-platform
for this.
Maybe you use something similar to this:
> Which package store is used by default depends on whether Octave is running
with admin rights.  On Unix-like system, that means that Octave is executing
as root (superuser).  On Windows, that means that it is running with elevated
privileges (i.e., with administrator rights).

After that, you could maybe just write "admin rights" to mean either of them.

Maybe, a native speaker could improve on that wording.

Also the point about package updates not getting (newly added) dependencies
first is news to me. Did you verify that this doesn't work?
Is there a bug report about that? Instead of documenting it, we should
probably better fix it if that doesn't work.


    _______________________________________________________

Reply to this item at:

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

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