Internally a package is simply a gzipped tar file that contains a
top level directory of any given name. This directory will in the
following be referred to as package and may contain the
following files
package/DESCRIPTIONpackage/COPYINGpackage/INDEXCategories keyword in the DESCRIPTION file.
See The INDEX File, for details on this file.
package/PKG_ADDPKG_ADD directives in the
source code of the package will also be added to this file by the
Octave package manager. Note that symbolic links are to be avoided in
packages, as symbolic links do not exist on some file systems, and so
a typical use for this file is the replacement of the symbolic link
ln -s foo.oct bar.oct
with an autoload directive like
autoload ('bar', which ('foo'));
See PKG_ADD and PKG_DEL Directives, for details on PKG_ADD
directives.
package/PKG_DELPKG_DEL directives in
the source code of the package will also be added to this file by the
Octave package manager.
See PKG_ADD and PKG_DEL Directives, for details on PKG_DEL
directives.
package/pre_install.mpackage/post_install.mpackage/on_uninstall.mBesides the above mentioned files, a package can also contain on or more of the following directories
package/instm-files.
package/srcmake if a file Makefile exists in this
directory. make install will however not be called. The
environment variables MKOCTFILE, OCTAVE_CONFIG, and
OCTAVE will be set to the full paths of the programs
mkoctfile, octave-config, and octave, respectively,
of the correct version when configure and make are
called. If a file called FILES exists all files listed there
will be copied to the inst directory, so they also will be
installed. If the FILES file doesn't exist, src/*.m and
src/*.oct will be copied to the inst directory.
package/docpackage/bin