Every installation of "findlib" has a default location for package
directories, which is normally a directory called "site-lib". The
location can be set by the configuration variables
(used to look up packages), and
(used to install new packages);
The name of a package is the name of the package directory. For
package p will be installed in the subdirectory
. This subdirectory
must contain the META file and all other files belonging to the package.
Package names must not contain the . character.
specifies the directory for
new packages. You can only have one such directory at a time; but of
course you can change this directory in findlib.conf. The command
puts new packages into this
directory; it is recommended to use this command for installation
because it ensures that the directory layout is right.
For searching packages, findlib uses (only) the variable
which may name several locations to look at.
For systems with DLL support another directory may exist: stublibs.
If present, findlib will install DLLs into this directory that is
shared by all packages at the same site-lib location. Findlib remembers
which DLL belongs to which package by special files with the suffix
".owner"; e.g. for the DLL "dllpcre.so" there is another file
"dllpcre.so.owner" containing the string "pcre", so findlib knows
that the package "pcre" owns this DLL. It is not possible that a DLL
is owned by several packages.
If the stublibs directory does not exist, DLLs are installed regularly
in the package directories like any other file.
For special needs, a postinstall and/or a postremove script may be
installed in the site-lib directory. These scripts are invoked after
installation or removal of a package, respectively.
...somewhere in the filesystem hierarchy...
+- (optional) stublibs
+- (optional) postinstall
+- (optional) postremove
This is an alternate directory layout collecting all META files in one
directory. You can configure this layout by setting
to the absolute location of
. Findlib recognizes that there are
META files in this directory and uses them; it is not necessary to
In order to work, the META files must contain a
directive pointing to the corresponding
package directory that resides below
copes with this
layout, too. The variable
must contain the
absolute location of
, and the variable
must contain the absolute location of
. Note that
automatically adds a
directive to the META file, so you need not do it manually.