Package Searching

Tools shall locate a package by searching for a file name.cps in the following paths:

  • environment-path/name-like/cps/

  • environment-path/name-like/

  • prefix/name-like/cps/ (Windows)

  • prefix/cps/name-like/ (Windows)

  • prefix/cps/ (Windows)

  • prefix/name.framework/Versions/*/Resources/CPS/ (macOS)

  • prefix/name.framework/Resources/CPS/ (macOS)

  • prefix/name.app/Contents/Resources/CPS/ (macOS)

  • prefix/libdir/cps/name-like/

  • prefix/libdir/cps/

  • prefix/share/cps/name-like/

  • prefix/share/cps/

The various placeholders are as follows:

name:

The name of the package to be located, including both the case as specified by the consumer, and the name converted to lower case.

name-like:

Any of name/* or name, where name is as previously defined, and the asterisk (*) is one or more valid filename characters, excluding the path separator. This is intended to allow multiple versions of a package to be installed into the same prefix.

libdir:

The platform defined directories, sans root prefix, in which matching architecture and/or architecture-neutral libraries reside (e.g. lib, lib32, lib64, lib/x86_64-linux-gnu…).

environment-path:

One of the set of paths (separated by ; on Windows, : otherwise) in the environment variable CPS_PATH. If CPS_PATH is empty, paths starting with environment-path are skipped.

prefix:

One of the set of default install prefixes to be searched, which shall include, at minimum and in order, the set of paths (separated by ; on Windows, : otherwise) in the environment variable CPS_PREFIX_PATH, /usr/local, and /usr.

All paths beginning with environment-path shall be searched in the order specified above, for each path in CPS_PATH, before the next such path is searched, and before any other paths are searched. All paths beginning with prefix shall be searched in the order specified above, for each prefix, before the next prefix is searched.

It is recommended that tools should also provide a mechanism for specifying the path to a specific CPS which may be used to override the default search, or to provide the location of a package which is not installed to any of the standard search paths.

When a candidate .cps file is found, the tool shall inspect the package’s platform. If the package’s platform does not match the target platform, the tool should ignore the .cps and continue the search. This allows for the installation of packages for different platforms (e.g. 32- and 64-bit builds) on a single machine. (Note that it is up to the tool to determine what constitutes a matching platform.) Similarly, if the package’s version does not satisfy the required version as specified by the user, the tool should continue searching. (In both cases, the tool may wish to make note of the incompatible packages, and the reason for rejection.)

Prefix Determination

In order to determine the package prefix, which may appear in various attributes as @prefix@, it is necessary to determine the effective prefix from the canonical location of the .cps file. This can be accomplished in three ways:

  • If the package specifies a cps_path, that value shall be used.

  • Otherwise, if the tool has just completed a search for the .cps, as described above, the prefix is known from the path which was searched.

  • Otherwise, the prefix shall be deduced as follows:

    • The path is initially taken to be the directory portion (i.e. without file name) of the absolute path to the .cps file.

    • (macOS) If the tail-portion matches /Resources/ or /Resources/CPS/, then:

      • The matching portion is removed.

      • If the tail-portion of the remaining path matches /Versions/*/, that portion is removed.

      • If the tail-portion of the remaining path matches /name.framework/ or /name.app/Contents/, that portion is removed.

    • Otherwise:

      • If the tail-portion of the path matches /cps/name-like/ or /cps/, that portion is removed.

      • If the tail-portion of the remaining path matches any of /libdir/ or /share/, that portion is removed.