Add an FAQ entry that recommends binary packages

While we provide and document our source tarball, we should clarify that
we recommend using distribution-provided binary packages whenever
possible.

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.
 * [How do I install the plugins?][installation]
 * [Why aren't the root plugins installed?][root-plugins]
 * [Which user owns the installed plugins?][ownership]
+* [Shouldn't I use a binary package instead?][packages]
 
 ## Development
 
@@ -55,6 +56,7 @@ Plugins.
 [installation]: doc/faq/installation.html
 [root-plugins]: doc/faq/root-plugins.html
 [ownership]: doc/faq/ownership.html
+[packages]: doc/faq/packages.html
 [git]: doc/faq/git.html
 [guidelines]: doc/faq/guidelines.html
 [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 @@
+title: Binary packages
+parent: FAQ
+---
+
+# Shouldn't I use a binary package instead?
+
+Short answer: **Yes**!
+
+Slightly longer answer:
+
+Most Linux distributions and BSD projects provide binary packages of the
+Nagios Plugins.  These are usually well-integrated and much easier to deploy
+and maintain, so we strongly recommend using them whenever possible.
+
+Our source tarballs and the associated documentation are primarily intended
+for package maintainers, for those users who'd like to test them, and for the
+rare occasions where using a binary package is not feasible for one reason or
+another.
+
+<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %-->