Overview of changes:

 *  Fixed build-time testing error

    FTBFSC error caused by SATURNIN_LIBEXEC not being overriden during
    build-time tests.

Otherwise tests can't pass, especially not on clean machine.

Overview of changes:

 *  Renamed Debian package name for saturnin_demo

    Underscore is apparently banned from package names in Debian.

Underscore does not seem to be allowed in Debian package names.

Overview of changes:

 *  Added saturnin-yell for sending severe messages

 *  Cleaned up packaging and meta-data

 *  Codebase maintenance

`%global` is preferred to `%define` according to FPG:

    https://fedoraproject.org/wiki/Packaging:Guidelines#.25global_preferred_over_.25define

Wrapper around three main functions from pretty.sh.  Useful to
demonstrate modularity of pretty.sh, eg:

    PRETTY=color saturnin-yell warn "you're doing it wrong"

will print the warning colored in the terminal, but

    PRETTY=color saturnin-yell warn "stop right now"

will send a desktop notification instead.

Overview of changes:

 *  Split to core+module package

    The package now demonstrates a slightly more complex (but more
    useful) distribution model, when part of functionality is also
    exposed as public API via Shellfu/Bash module.

 *  Fixed PRETTY_DEBUG_EXCLUDE not being applied

 *  Improved and fixed packaging meta-data

 *  Codebase maintenance

It has no effect in subcommands otherwise.

Split saturnin-demo to a double-package distribution, where one package
provides core saturnin-demo with its subcommands and the other provides
a Shellfu/Bash module saturnin_demo_greet.sh used by the first one.

It's GPLv2, really.

Overview of changes:

 *  Removed SHELLFU_PATH from default setup

    People are encouraged to put Shellfu modules to standard paths
    anyway (where they can be seen by sfdoc), so this is not very
    useful.  We better get rid of it, taking another (path-related,
    ie. unreliable) token out of mkit.ini.  There's always option
    of modifying app.skel or re-setting the path dynamically (from
    sub-command or by a wrapper), if someone is so ashamed of their module
    (but don't be!).

 *  Hardcoded default name of help file

    Removes the one token that was missing in mkit.ini anyway, causing
    false ugly errors to be thrown at real users.  Again, if people can't
    really use that name, they can alwas modify (or wrap) app.skel.

 *  app.skel now respects SATURNIN_CONF_PATH from environment.

    Ie. tests should work even with v0.4.9+

 *  Moved app.skel right under src

    There's virtually never anything else there.

 *  Added example meta help file

 *  Simplified and cleaned up mkit.ini

 *  Removed unnecessary override in %check

 *  Updated MKit to v0.0.25

Tests are supposed to set it on their own and not rely on environment.
Hence it's not even interesting to have in TF_HEADER.

Turns out that leaving this to saturnin__conf_mkpath() is not so good
idea.

There's no real need to list every file.

SHELLFU_PATH brings more harm than good; developers are encouraged to
put their private modules to regular shellfu path (in most cases
/usr/share/shellfu/include-*) and use SHELLFU_PATH only for testing.
It's a bit simpler (gets rid of one whole token) and has the advantage
of exposing the library to sfdoc.

MKit (as of 0.0.25, and probably for long time in furure) ignores tokens
not defined in mkit.ini, so app developer has to either define it or
their users will see errors on every `app --help call`.

This way we can remove the need to define yet another token.

With most Saturnin setups there won't be anything else in bin anyway.

Require merge to 'master' prior to version bump and update 'last' after
release.

Overview of changes:

 *  Added build-time tests

    Saturnin Demo now demonstrates how to add tests using TFKit and
    enable them on both Fedora and Debian.  (This means dependency bump
    to Saturnin 0.4.8, since overriding SATURNIN_CONF_PATH was not
    available, which made config-related tests hard in staged
    installations.)

 *  Enabled overriding path variables in launcher

    Launcher used to hard-code all environment variables.  This made
    testing in staged installations hard.

 *  Updated meta-data and templates

    An amount of smaller changes has been done to improve readability,
    maintainability and overall looks of packaging meta-data.

This requires newer Saturnin version in order to avoid bug where
SATURNIN_CONF_PATH environment variable would be ignored.

Several changes to improve maintainability, readability and style of
packaging meta-data:

 *  Use more maintainable syntax in templates.  That is, more MKit macros,
    line-based lists, etc.

 *  Use Markdown for LICENSE.

 *  Use normal case (don't YELL) in application name.

 *  Use only spaces to align spec file.

 *  Use version ranges for SemVer dependencies.

 *  Sort %files section.

 *  Use shorter version level (0.y vs 0.y.z) in ranges where possible

 *  Move MKit compatibility directive to bottom (which actually changes
    the compatibility level to 0.0.24 as older MKit had a bug that
    prevented seeing the directive near the bottom.)

Having them strictly hard-coded makes it difficult to write system tests
test in staged install scenarios.

Overview of changes:

 *  Excluded inigrep as well as saturnin itself from normal debugging mode

    One has to call -D|--full-debug to see the gory inigrep/saturnin stuff.
    Normal debug is supposed to be used for things relevant to
    subcommand scripts.

 *  Moved to /usr

 *  Added --full-debug and -V to tab completion script

 *  Many code and packaging clean-ups

 *  Updated for Saturnin v0.4.7

 *  Updated for Shellfu v0.10.1

 *  Updated MKit to v0.0.24

It makes a lot of noise that is normally not very relevant to the
application.

They made sense when the script was bigger, now they delimit basically
the whole script.  Also "built part" is not accurate since the part is
not built--it only happens to contain lot of macros.

Saturnin Shellfu module used to be embedded into the repo; now it lives
its own life (we already have it in dependencies).  All the app needs is
meta-command and scripts.