octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #59821] [octave forge] (ga) pkg update with ga


From: Nicholas Jankowski
Subject: [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
Date: Tue, 5 Jan 2021 12:15:35 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36

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

sorry for the comment flood

in reverse order- 
unless I'm reading the code wrong I don't see how pkg update can be affected
by -global. for each pkg to update it calls

pkg install -forge <pkgname>

and the package name is just its short-name (audio, etc.) so the global flag
is ignored.  I'll need to remove that suggestion from the wiki. it doesn't
look possible to pass any options to update

stepping through the package update info collection, things just look stranger
yet.  my pkg local_list is C:\Users\NICHOL~1.JAN\.octave_packages

and the initial pkg update updated the two global packages with local updates
in C:\Users\NICHOL~1.JAN\octave

but after the series of pkg updates, etc. mentioned below the two packages in
the local_packages list have locations set to, e.g., 

C:\Programs\Octave\octave-6.1.0-w64\mingw64\share\octave\packages\nan-3.5.2

so, somehow both my local and global lists are pointing to the same global
packages?  I didn't make any manual prefix changes or anything I can see
explaining this. And I'm always just running as a user.  I think I might just
delete and re-extract the archive and see if I can reproduce any of this.

regarding the other points:  previously, at least the zip archive windows
versions always made changes to global packages using default configuration, I
don't know about the exe installer and whether its behavior depended on root
privileges or install location. but some of the help text makes reference to
needing write access to do global installs, but the automatic check is really
for user-admin level, not write access. so maybe some doc clarification needed
there since those aren't interchangeable.

last, will re-tweak/correct the wiki.



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]