-
Notifications
You must be signed in to change notification settings - Fork 1
/
INSTALL
69 lines (45 loc) · 2.26 KB
/
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
To install certtools:
Required tools:
GNU bash, Make and perl
basic POSIX tools, including:
tar, install
Strongly recommended:
gpg
You do NOT need to clone the repository unless you want to submit patches.
Obtain a release tarball from https://github.com/tlhackque/certtools
- Look for the "Releases" note on the right side of the page, and click "Latest"
- Under "Assets", click a versioned tarball and corresponding signature link
(Or download using a command line tool such as wget or curl)
e.g. if the latest release is V2.1.2, you could obtain it with:
wget htps://github.com/tlhackque/certtools/releases/download/V2.1.2/certtools-2.1.2.tar.xz
wget htps://github.com/tlhackque/certtools/releases/download/V2.1.2/certtools-2.1.2.tar.xz.sig
Verify and unpack the tarball, e.g.
gpg --verify certtools-2.1.2.tar.xz.sig && tar -xf certtools-2.1.2.tar.xz && cd certtools-2.1.2
To install in the default locations (/usr/local/sbin and /usr/local/share/man/man1):
make install
The installer will check for Perl modules that are required by the Perl-based tools. If any
are missing or too old, it wil provide instructions for obtaining them.
To install in an alternate root, e.g. /opt:
make prefix=/opt install
To stage when incorporating in a larger system kit:
DESTDIR=/opt/stage make
DESTDIR=/opt/stage prefix=/usr
For more complex requirements, see the Makefile.
You can delete the directory into which you unpacked the release.
Note that the release tarball does not include the .md version of the documentation;
these are provided for easy browsing on GitHub. The contents are the same as the man
pages and the --man (or -h) output from the tools. --man (for the Perl tools) and -h
(for the bash tools) are preferred, since they can't be separated from their tool.
Building release kits requires additional tools:
If the necessary tools can't be found on PATH, make variables can be
set for each one in the make invocation - though if necessary for more
than one or two, it's better to set an appropriate PATH.
From CPAN:
cpan install Pod::Checker Pod::Markdown
Options:
cpan install Perl::Tidy
shellcheck (see https://www.shellcheck.net/)
GNU tools:
make, sed
basic POSIX tools, including:
tar, head, cp, date, chmod, chown, mkdir, rm, install, echo, tee