installPackage -- load and install a package and its documentation

Synopsis

• Usage:

  installPackage PACKAGENAME

• Inputs:
  • PACKAGENAME, a String or Package
• Optional inputs:
  • FileName => a string, default value null, the name of the file containing the source code of the package, from which it should be loaded
  • UserMode => default value null, if true, then do not give the -q option to M2 when running examples, thereby allowing it to load the user's initialization file, allowing it to load packages previously installed in the user's application directory, and allowing packages it loads to read their configuration files from the the user's application directory. If false, then do give the option. If null, then propagate the option from the current commandLine, if one occurs there.
  • DebuggingMode => a Boolean value, default value null, whether to enter the debugger if an error occurs during installation; however, if debuggingMode is already false, it will remain so.
  • RerunExamples => a Boolean value, default value false, whether to rerun all the examples during installation
  • RunExamples => a Boolean value, default value true, whether to run the examples during installation
  • IgnoreExampleErrors => a Boolean value, default value false, whether to ignore errors that occur during the running of examples during installation
  • CheckDocumentation => a Boolean value, default value true, whether to check the package's documentation for consistency and completeness
  • MakeDocumentation => a Boolean value, default value true, whether to make the documentation for the package during installation
  • MakeInfo => a Boolean value, default value true, whether to make the info pages. This is a form of the documentation that can be viewed using the Unix command info or using emacs.
  • InstallPrefix => default value -*Function[/home/dan/src/M2/M2/Macaulay2/m2/installPackage.m2:384:31-384:57]*-, the installation prefix for installation of the files of the package, in case encapsulation is not enabled, or for installation of the links to the files, in case encapsulation is enabled. The value of this option can be a string or a function of no arguments returning a string. The default value is the subdirectory named local of the user's application directory.
  • MakeLinks => a Boolean value, default value true, whether to make links to the files after installing them, in case encapsulation is enabled
  • RemakeAllDocumentation => default value true, whether to regenerate all of the help pages for this package. The default action is to rebuild only the html pages of the documentation entries that have been changed since the last time the package was installed. However, some changes to an entry, such as to its headline, will change the html of other pages that cross-reference it.
  • CacheExampleOutput => a Boolean value, default value null, whether to cache (newer) example output in a subdirectory of the auxiliary file directory named examples, for use in a future installation. This value, if set to true or false, will override any value explicitly specified when newPackage is called. After the directory is created, it will be necessary for the user to specify AuxiliaryFiles=>true with the newPackage command.
  • SeparateExec => a Boolean value, default value false, whether to install the files of the package in two separate directory trees, one for the architecture independent files, and one for the architecture dependent files
  • Verbose => a Boolean value, default value true, whether to display some details of the installation procedure. For even more information set debugLevel to a number greater than 0 or a number greater than 5.
• Outputs:
  • a package, the package that was installed
• Consequences:

  • The package is installed in a local directory, so that in the future, one may simply use loadPackage. Documentation for the package is also produced, running any Macaulay2 examples that are requested in the package documentation, with the random number seed initialized to 0.

Description

The main action of this routine is to generate the documentation of the given package and install the Macaulay2 package and documentation.

The actual file loaded is PACKAGENAME.m2, which should be on the load path and should contain a package named PACKAGENAME.

In order to accomplish this, several steps are performed (or bypassed, depending on the values of the optional arguments).

• load the package, if not already loaded (see loadPackage)
• determine which help pages have changed since last install
• run any new or previously failed examples, or all examples, as specified by the RemakeAllExamples (missing documentation) option
• generate the html pages of modified help pages, or all html pages, as specificed by the RemakeAllDocumentation option
• generate the info pages, or not, as specified by the MakeInfo option
• install the documentation and package in the location specified by the InstallPrefix option
• place a link to this html documentation in the file index.html in the user's application directory; see makePackageIndex

The current value of prefixPath is used to determine how to direct documentation hyperlinks; the link will be directed to the appropriate file if one is found by searching the trees referred to by prefixPath. Otherwise, all documentation hyperlinks are relative to positions within a single tree of directories, as describe by Layout.

It might be necessary to run installPackage twice if a package with the same name is already installed: the second installation will redirect the hyperlinks to the freshly installed documentation, because the files will have been installed by the first installation. This applies, for example, to those authors who are developing updates to packages already included with Macaulay2.

The files of the package are placed in subdirectories of the appropriate prefix directory as specified by Layout, depending on the value of the SeparateExec option: when it is false the files are all in share/Macaulay2/PACKAGENAME.m2, share/info/PACKAGENAME.info, lib/Macaulay2/PACKAGENAME/, share/Macaulay2/PACKAGENAME/, and share/doc/Macaulay2/PACKAGENAME/; when it is true the paths to the files are modified to reflect the type of your machine, e.g., common/share/Macaulay2/PACKAGENAME.m2, common/share/info/PACKAGENAME.info, x86_64-Linux-Ubuntu-18.04/lib/Macaulay2/PACKAGENAME/, common/share/Macaulay2/PACKAGENAME/, and common/share/doc/Macaulay2/PACKAGENAME/.

In addition, if no errors occurred during running the examples, then an empty file whose name is lib/Macaulay2/PACKAGENAME/.installed or x86_64-Linux-Ubuntu-18.04/lib/Macaulay2/PACKAGENAME/.installed is created, to signify that installation was completed.

Caveat

Links from html files containing documentation to documentation in another package not yet installed may go to the wrong place, because it is assumed that the package not yet installed will be installed under the same prefix. By contrast, if the other package has already been installed under some prefix occurring in the value of prefixPath, then the correct path will be used. To get two packages installed under different prefixes which refer to each other's documentation correctly, it may be necessary to install one of them twice.

See also

• packages
• epkg
• prefixPath -- absolute locations of Macaulay2 files
• Layout -- relative locations of Macaulay2 files
• installedPackages
• uninstallAllPackages