backup.sh v0.3.1

backup.sh v0.3.1

This release fixes behavior of the consume verb. Previously, different
passes of the consume verb did not reset the prune engine state. This
led to the pruning step not working as expected: any pruning rule that
matched any existing scheduling rule in a consumer job would not be
considered by the consume verb implementation.

Additionally, the pruning engine and the consume verb were optimized
for performance.

backup.sh v0.3.0

backup.sh v0.3.0

This release adds support for extracting and loading configuration
function dependencies. Now, if a configuration function declared in a
Backupfile calls another function (not necessarily prefixed with the job
name) it will also be loaded.

Note that caution must be exercised to avoid overwriting backup.sh
internal functions. This may be changed in future to require function
names be prefixed with a namespace string to be considered for loading.

backup.sh v0.2.4

backup.sh v0.2.4

This release cleans up logging prefix handling, such that it is kept
consistent when backup.sh calls itself during a single run.

backup.sh v0.2.3

backup.sh v0.2.3

This release adds support for (non-upstreamed) borg --lock-rc option
to recognize when a borg job has failed due to the inability to acquire
a lock, and adds support in bsh run-all to recognize such conditions.

Additionally, logging in bsh run-all was refactored to better reflect
the decision process that leads to each job being skipped or failed.

backup.sh v0.2.2

backup.sh v0.2.2

This release contains another hot-fix to bsh run-all, making it
retrieve the job's SOURCE configuration correctly.

backup.sh v0.2.1

backup.sh v0.2.1

This release fixes bsh run-all after configuration engine changes in
v0.2.0. Additionally, bsh unmount does not fail if no mountpoints are
present in the given tree.

backup.sh v0.2.0

backup.sh v0.2.0

This release makes a breaking change in configuration variable naming.
In the new format, BTRFS_, btrfs_, BORG_ and borg_ prefixes are not used
in configuration variables and functions.

Additionally, configuration loading has been made more robust and strict
in face of invalid configuration.

backup.sh v0.1.0

Nearly a complete rewrite of all supporting logic and configuration file parsing.

Configuration changes:

• there is a single toplevel configuration file called Backupfile
• jobs may share the toplevel configuration file or be placed in separate files that are referenced from the toplevel
• jobs are referred to by name, not by their configuration file path
• configuration of all job's aspects (prune, schedule) is now unified
• configuration files are loaded in a clean, separate subshell
• well-defined functions for loading or locating other files are provided in the configuration file environment

CLI changes:

• there is a single entrypoint script called backup.sh or bsh
• all operations with bsh follow the same syntax of bsh <VERB> [JOB [ARGS...]]
  (except for bsh unmount which takes ARGS but not JOB)

Packaging changes:

• a PKGBUILD is provided (installation is open-coded, no Makefile yet)