153
edits
Octave for Microsoft Windows: Difference between revisions
Jump to navigation
Jump to search
→Package Installation and Update
(→Octave Packages: corrected information about update -global) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 29: | Line 29: | ||
>> pkg global_list | >> pkg global_list | ||
Octave versions for Windows prior to 6.1.0 defaulted to always | Octave versions for Windows prior to 6.1.0 defaulted to always making changes to global packages unless the user specified otherwise. The default is now to follow the same behavior on all platforms, and for all package updates and installations to apply to local or global package locations according to whether or not the user is running with Administrative privileges (on Windows, this is usually accomplished by running as an Administrator privileged account, or starting Octave with the "Run as Administrator" option). Alternatively, some pkg command options can force octave to try to use either the local or global packages. | ||
===Pre-installed Packages=== | ===Pre-installed Packages=== | ||
| Line 111: | Line 111: | ||
>> pkg install package_file_name.tar.gz | >> pkg install package_file_name.tar.gz | ||
Note that all of the commands above will perform ''local'' or ''global'' package installs according to the user's Administrator access level. E.g., if an update is found for a global package with a non-elevated user, the updated version will be installed to the ''local'' package location, leaving the old version intact in the ''global'' package location. This behavior can be changed by calling the install command with the {{Path|-global}} option. For example: | Note that all of the commands above will perform ''local'' or ''global'' package installs according to the user's Administrator access level. E.g., if an update is found for a global package with a non-elevated user account, the updated version will be installed to the ''local'' package location, leaving the old version intact in the ''global'' package location. This behavior can be changed by calling the install command with the {{Path|-global}} option. For example: | ||
To install a global package to the latest version (requires write-access to the global-list location) you can use: | To install a global package to the latest version (requires write-access to the global-list location) you can use: | ||
| Line 117: | Line 117: | ||
>> pkg install -forge -global <package_name> | >> pkg install -forge -global <package_name> | ||
Note that the update command does not take -local or -global options, and always performs an update according to the user's Administrator access level. | Note also that the update command does not take -local or -global options, and always performs an update according to the user's Administrator access level. As such if Octave was installed from a zip or 7z archive in a non-privileged account, 'pkg update' cannot be used to update global packages, they must be updated manually using 'pkg install' | ||
Detailed instructions for installing individual Octave Forge packages are given at https://octave.sourceforge.io/packages.php. | Detailed instructions for installing individual Octave Forge packages are given at https://octave.sourceforge.io/packages.php. | ||