For situations when there are constraints on what characters are
allowed, this module provides several non-reversible conversion
functions.

Prefer `%global` over `%define` and do it earlier.

Turns out moving sfdoc code to dedicated module *and* having the binary
in main package created cyclic dependecy.  However, there's easy way out;
let's just run with it as long as it works on most distros.

source-highlight is not necessary (-s|--src will fall back to plain text
if it's missing) and requiring it strictly breaks RHEL6 build.

deb users can follow Suggests field; rpm users will have to find out about
it and install it separately.  (Optional requires do exist in newer RPM,
but it's not worth the effort/ifdef bloat.)

Allow for re-use and more independent testing.

Tested on Fedora, praying for it to work on Debian.

Otherwise we're not really testing "this" shellfu but the installed one.

Add missing perl and ps dependencies and remove bash (because Essential
packages are not supposed to be there).

Switch to packaging model where each module goes into separate package.

Such model makes much more sense (after all it's also how big platforms
such as python do it).  It allows better control over dependencies and
allows re-locating modules properly according to compatibility level
(i.e. now exit.sh can go to 'sh' despite the fact that in 'core' it had
to be with other Bash-compatible modules).

Not used anywhere these days

Mostly for consistency with the other two binaries.

'sfdoc' is easier to type and resembles 'pydoc' and 'perldoc' so it's
even easier to remember.

The only purpose of the binary is to show local Shellfu path and it's
in every single Shellfu script.  Let's save people some typing.

Also a first POSIX-oriented library!

Used to declare POSIX orientation (in terms od Shellfu), plus to hold
'include-sh' directory on RPM-based distributions.

Turns out that since shellfu-doc uses pretty.sh (and makes good use of
it), what we had was broken cyclic dependency.

shellfu-doc and shellfu-embed are useful mostly for developers, though,
so it's no shame to split them.