== Available vs Loaded ==
To avoid problems reading
thuis document, the distinction between having a package available and a package loaded will be done from the start. An available package is a package that is currentlyavailable to pkg to load, unload or reinstall. It is already installed but not necessarily loaded.
A loaded package is an installed package whose functions have been added to Octave's function search
=== Global installs ===
The meaning of global is relative to the Octave installation. If an Octave installation is local, a global
installation of a package will still place its files in the home directory of the user ( something like~/usr/local/ or whatever was defined when running Octave's installation configure script). Anyone running this Octave installation will have them available ( not loaded) from Octave startup.
A package globally installed is available globally to that
=== Local installs ===
=== External installs ===
== Package names ==
be loaded? I'd propose the default to be:
# load the latest version availale # load the local install of the package # load the global install of the package # load the package from the external .db, starting from the latest added in case there's more than one.
For package names, the proposal is to limit package names to the same as variable
sensitive (creating directories named Image and image would not be possible in FAT
== User cases ==