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

[Nicholas Jankowski]

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

yes, the code checks the user's role at the start and sets 'global_install'
accordingly.  the -global/local switch forces global_install to true or false
regardless of the check.  it will try to perform installs accordingly whether
access actually exists or not, with a permissions error if it tries to write
where it cannot. The only text changed for the global/local options is the
naming of the superuser role, leading to you other point: 

I thought the second patch made this clarification as you suggested in comment
#25:
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).

with the following revised text:

 
Global packages are installed by default in a system-wide location.  This is
usually a subdirectory of the folder where Octave itself is installed.
Therefore, Octave needs write access to this folder to install global
packages, which is usually only available when Octave is run with 
administrative rights.  That means to install packages globally Octave checks
if 
it is executing as root (superuser) on Unix-like systems, or it is running
with elevated privileges ("Run as administrator") on Windows.


it attempts to use administrative rights in a general sense for the rest of
the help after defining what that means on linux and windows. 

Did i misinterpret?



    _______________________________________________________

Reply to this item at:

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

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