‣ InstallPackage( string[, version][, interactive] ) | ( function ) |
Returns: true or false
Attempts to download and install a package. The argument string should be a string containing one of the following:
the name of a package;
the URL of a package archive, ending in .tar.gz or .tar.bz2;
the URL of a git repository, ending in .git;
the URL of a valid PackageInfo.g file.
The package will then be downloaded and installed, along with any additional packages that are required in order for it to be loaded. Its documentation will also be built if necessary. If this installation is successful, or if this package is already installed, true is returned; otherwise, false is returned.
By default, packages will be installed in the pkg subdirectory of the user's home directory, see UserHomeExpand (Reference: UserHomeExpand). Note that this location is not the default user pkg location on Mac OSX, but it will be created on any system if not already present. Note also that starting GAP with the -r flag will cause all packages in this directory to be ignored.
Certain decisions, such as installing newer versions of packages, will be confirmed by the user via an interactive shell – to avoid this interactivity and use sane defaults instead, the optional argument interactive can be set to false.
To see more information about this process while it is ongoing, see InfoPackageManager (2.2-1).
If string is the name of the package in question then one can specify a required package version via a string as value of the optional argument version, which is interpreted as described in Section Reference: Version Numbers. In particular, if version starts with = then the function will try to install exactly the given version, and otherwise it will try to install a version that is not smaller than the given one. If an installed version satisfies the condition on the version then true is returned without an attempt to upgrade the package. If the package is not yet installed or if no installed version satisfies the version condition then an upgrade is tried only if the package version that is listed on the GAP webpages satisfies the condition. (The function will not update a dev version of the package if a version number is prescribed; otherwise it could happen that one updates the installation and afterwards notices that the version condition is still not satisfied.)
If installation fails, then any new directories that were created will be removed. To override this behaviour, the option keepDirectory can be set to true using, for example, InstallPackage("example" : keepDirectory), in which case such directories will be preserved for debugging.
gap> InstallPackage("digraphs"); true
‣ UpdatePackage( name[, interactive] ) | ( function ) |
Returns: true or false
Attempts to update an installed package to the latest version. The first argument name should be a string specifying the name of a package installed in the user GAP root (for example, one installed using InstallPackage (2.1-1)), see Reference: GAP Root Directories. The second argument interactive is optional, and should be a boolean specifying whether to confirm interactively before any directories are deleted (default value true).
If the package was installed via archive, the new version will be installed in a new directory, and the old version will be deleted. If installed via git, it will be updated using git pull, so long as there are no outstanding changes. If no newer version is available, no changes will be made.
This process will also attempt to fix the package if it is broken, for example if it needs to be recompiled or if one of its dependencies is missing or broken.
Returns true if a newer version was installed successfully, or if no newer version is available. Returns false otherwise.
gap> UpdatePackage("io"); #I io version 4.6.0 will be installed, replacing 4.5.4 #I Saved archive to /tmp/tm7r5Ug7/io-4.6.0.tar.gz Remove old version of io at /home/user/.gap/pkg/io-4.5.4 ? [y/N] y true
‣ RemovePackage( name[, interactive] ) | ( function ) |
Returns: true or false
Attempts to remove an installed package using its name. The first argument name should be a string specifying the name of a package installed in the user GAP root, see Reference: GAP Root Directories. The second argument interactive is optional, and should be a boolean specifying whether to confirm certain decisions interactively (default value true).
Returns true if the removal was successful, and false otherwise.
gap> RemovePackage("digraphs"); Really delete directory /home/user/.gap/pkg/digraphs-0.13.0 ? [y/N] y true
‣ InstallRequiredPackages( ) | ( function ) |
Returns: true or false
Attempts to download and install the latest versions of all packages required for GAP to run. Currently these packages are GAPDoc, primgrp, SmallGrp, and transgrp. Returns false if something went wrong, and true otherwise.
Clearly, since these packages are required for GAP to run, they must be loaded before this function can be executed. However, this function installs the packages in the ~/.gap/pkg directory, so that they can be managed by PackageManager in the future, and are available for other GAP installations on the machine.
‣ InfoPackageManager | ( info class ) |
Info class for the PackageManager package. Set this to the following levels for different levels of information:
0 - No messages
1 - Problems only: messages describing what went wrong, with no messages if an operation is successful
2 - Directories and versions: also displays informations about package versions and installation directories
3 - Progress: also shows step-by-step progress of operations
4 - All: includes extra information such as whether curlInterface is being used, and package info validation
Set this using, for example SetInfoLevel(InfoPackageManager, 1). Default value is 3.
‣ CompilePackage( name ) | ( function ) |
Returns: true or false
Attempts to compile an installed package. Takes one argument name, which should be a string specifying the name of a package installed in the user GAP root (for example, one installed using InstallPackage (2.1-1)), see Reference: GAP Root Directories. Compilation is done automatically when a package is installed or updated, so in most cases this command is not needed. However, it may sometimes be necessary to recompile some packages if you update or move your GAP installation.
Compilation is done using the etc/BuildPackages.sh script bundled with PackageManager. If the specified package does not have a compiled component, this function should have no effect.
Returns true if compilation was successful or if no compilation was necessary. Returns false otherwise.
gap> CompilePackage("orb"); #I Running compilation script on /home/user/.gap/pkg/orb-4.8.3 ... true
generated by GAPDoc2HTML