motoconf is a function written in, and for, POSIX sh. It follows that it needs such a shell to be useful.
These are used to build and (optionally) test and document motoconf.
Both Docutils and Cram imply a Python interpreter. Docutils is used to generate HTML version of README.rest and this file. Cram is used to drive the functional testsuite.
Packages for ArchLinux, CentOS, Fedora, Redhat, SUSE, ScientificLinux and openSUSE are available from the openSUSE Build Service (OBS).
The abovementioned packages are built using the package descriptions provided with motoconf. motoconf.spec supports rpm-based distros, PKGBUILD is used to create packages for ArchLinux. Instructions on using these are beyond the scope of this document.
Most prominent make(1) targets:
check
Run the test suite.
all
Build the program and its manual page, and convert reSt files to HTML.
most
Like all, but skip the reSt-to-HTML conversion.
install
Install the program and its manual page.
The GNUmakefile is parameterized with the usual macros (and then some). Notably, PREFIX (defaults to /usr/local) and DESTDIR (empty by default) are used to derive installation paths. Buildtime PATH is sanitized to {,/usr}/{,s}bin by default. If this is too tight for your system (eg. FreeBSD) you will need to pass the correct value on the command line.
Let's say your system has Cram installed as cram3 and the default PATH value used by the makefile prevents make from finding some tools. To build the artifacts and run the tests:
make check PREFIX=/usr CRAMCMD=cram3 PATH="$PATH"
To install the artifacts (PREFIX must be the same during build and install):
sudo make install PREFIX=/usr DESTDIR=/tmp/fakeroot