build

The build file is executed in the directory containing the package's extracted sources. Unlike other distributions, a cd is not needed as sources have their top-level directory components stripped away.

The build file is given two arguments: the destination directory (where artifacts should be installed) and the first field of the package's version file (verbatim).

The build file is given a modified environment containing DESTDIR, KISS_ROOT, GOPATH and generic defaults for toolchain variables (if unset by the user). The toolchain defaults are as follows:

AR=ar
CC=cc
CXX=c++
NM=nm
RANLIB=ranlib
RUSTFLAGS="--remap-path-prefix=$PWD=. $RUSTFLAGS"
GOFLAGS="-trimpath -modcacherw $GOFLAGS"

checksums

The checksums file is generated by the package manager (‘kiss c pkg’) and is derived from files listed in the package's sources file. Directories and git repositories do not require checksums.

Checksum verification can be disabled for a source by replacing its checksum with 'SKIP' in the checksums file. The package manager will notify you when this occurs.

depends

The depends file contains the package's dependencies listed one per line in alphabetical order. Duplicate entries are not supported. The second optional field denotes the dependency type (unset for runtime, “make” for compile-time). Lines beginning with ‘#’ are comments.

sources

The sources file contains the package's sources one per line. A valid source is a URL to a file, relative path, absolute path or Git repository. The optional second field denotes the relative destination directory. Lines beginning with ‘#’ are comments.

Git repositories must be prefixed with ‘git+’. An optional suffix is supported to checkout a specific branch (‘@BRANCH’) or commit (‘#COMMIT’). All clones are shallow where supported by the remote server. If no suffix is used, master is cloned.

The following markers can be used to substitute version information. These are replaced at runtime with their respective values. Literal markers can be escaped by prepending a backslash.

version

The version file is a single line split into two mandatory fields. The first field is the package's version and the second field the version of the repository files themselves.

If the package follows its upstream release schedule, the first field should match the upstream version number. If the source is a Git repository, the version should be set to ‘git’. If a specific git commit is used, the version number should match accordingly.

pre-remove

The pre-remove file is executed before removal of the package. This file should be used to perform any required pre-removal steps or to display notices.

post-install

The post-install file is executed after installation of the package. This file should be used to perform any required post-install steps or to display notices.