INSTALL


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82

Build Instructions
------------------

* Requirements
  ------------

  - A set POSIX-compliant and OS specific utils, see https://0x53.net/software/requirements.html
  - execline https://skarnet.org/software/execline/
  - s6 https://skarnet.org/software/s6/
  - s6-rc https://skarnet.org/software/s6-rc/
  - s6-linux-init https://skarnet.org/software/s6-linux-init/

This software will run on any operating system
that runs the requirements above.


* Standard usage
  --------------

  ./configure && make && make install

will work for most users.


* Customization
  -------------

You can customize paths via flags given to configure.
See ./configure --help for a list of all available configure options.

* Make variables
  --------------

You can invoke make with a few variables for more configuration.

INSTALL can be overridden on the make command line. This is
an even bigger hammer than running ./configure with environment
variables, so it is advised to only do this when it is the only way of
obtaining the behaviour you want.

DESTDIR can be given on the "make install" command line in order to
install to a staging directory.

* The slashpackage convention
  ---------------------------

The slashpackage convention (http://cr.yp.to/slashpackage.html)
is a package installation scheme that provides a few guarantees
over other conventions such as the FHS, for instance fixed
absolute pathnames. skarnet.org packages support it: use the
--enable-slashpackage option to configure, or
--enable-slashpackage=DIR for a prefixed DIR/package tree.
This option will activate slashpackage support during the build
and set slashpackage-compatible installation directories.
If $package_home is the home of the package, defined as
DIR/package/$category/$package-$version with the variables
read from the package/info file, then:

  --bindir is set to $package_home/command
  --sbindir is also set to $package_home/command (slashpackage
differentiates root-only binaries by their Unix rights, not their
location in the filesystem)
  --libdir is set to $package_home/

 --prefix is pretty much ignored when you use --enable-slashpackage.
You should probably not use both --enable-slashpackage and --prefix.

When using slashpackage, two additional Makefile targets are
available after "make install":
 - "make update" changes the default version of the software to the
freshly installed one. (This is useful when you have several installed
versions of the same software, which slashpackage supports.)
 - "make global-links" adds links from /command and /library.so to the
default version of the binaries and shared libraries.


* Out-of-tree builds
  ------------------

This package does not support out-of-tree builds. It
is small, so it does not cost much to duplicate the entire
source tree if parallel builds are needed.