diff options
-rw-r--r-- | web/input/doc/faq/index.md | 2 | ||||
-rw-r--r-- | web/input/doc/faq/packages.md | 20 |
2 files changed, 22 insertions, 0 deletions
diff --git a/web/input/doc/faq/index.md b/web/input/doc/faq/index.md index 35f6e75..722362c 100644 --- a/web/input/doc/faq/index.md +++ b/web/input/doc/faq/index.md | |||
@@ -28,6 +28,7 @@ Plugins. | |||
28 | * [How do I install the plugins?][installation] | 28 | * [How do I install the plugins?][installation] |
29 | * [Why aren't the root plugins installed?][root-plugins] | 29 | * [Why aren't the root plugins installed?][root-plugins] |
30 | * [Which user owns the installed plugins?][ownership] | 30 | * [Which user owns the installed plugins?][ownership] |
31 | * [Shouldn't I use a binary package instead?][packages] | ||
31 | 32 | ||
32 | ## Development | 33 | ## Development |
33 | 34 | ||
@@ -55,6 +56,7 @@ Plugins. | |||
55 | [installation]: doc/faq/installation.html | 56 | [installation]: doc/faq/installation.html |
56 | [root-plugins]: doc/faq/root-plugins.html | 57 | [root-plugins]: doc/faq/root-plugins.html |
57 | [ownership]: doc/faq/ownership.html | 58 | [ownership]: doc/faq/ownership.html |
59 | [packages]: doc/faq/packages.html | ||
58 | [git]: doc/faq/git.html | 60 | [git]: doc/faq/git.html |
59 | [guidelines]: doc/faq/guidelines.html | 61 | [guidelines]: doc/faq/guidelines.html |
60 | [c-apis]: doc/faq/private-c-api.html | 62 | [c-apis]: doc/faq/private-c-api.html |
diff --git a/web/input/doc/faq/packages.md b/web/input/doc/faq/packages.md new file mode 100644 index 0000000..2329db9 --- /dev/null +++ b/web/input/doc/faq/packages.md | |||
@@ -0,0 +1,20 @@ | |||
1 | title: Binary packages | ||
2 | parent: FAQ | ||
3 | --- | ||
4 | |||
5 | # Shouldn't I use a binary package instead? | ||
6 | |||
7 | Short answer: **Yes**! | ||
8 | |||
9 | Slightly longer answer: | ||
10 | |||
11 | Most Linux distributions and BSD projects provide binary packages of the | ||
12 | Nagios Plugins. These are usually well-integrated and much easier to deploy | ||
13 | and maintain, so we strongly recommend using them whenever possible. | ||
14 | |||
15 | Our source tarballs and the associated documentation are primarily intended | ||
16 | for package maintainers, for those users who'd like to test them, and for the | ||
17 | rare occasions where using a binary package is not feasible for one reason or | ||
18 | another. | ||
19 | |||
20 | <!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %--> | ||