Changes

Jump to navigation Jump to search
Line 29: Line 29:  
     >> pkg global_list
 
     >> pkg global_list
   −
Octave versions for Windows prior to 6.1.0 defaulted to always using and making changes to global packages.  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 running 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.
+
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===
110

edits

Navigation menu