…s that the files in one or more of the directories that are being archived have changed since the archive was being read by the `tar` utility. This can happen when a folder that's constantly updated by for example user data from a website (e.g. user uploads) and you do not want backup to abort every single time someone uploads a new file during the archiving process. The new file will be picked up during the next backup process and ignored during the current one rather than aborting the whole backup operation.
…n and method since the CommandFailed exception already picks it up, and it isn't necessary to check whether the command isn't found twice. Also, it is now possible to pass in an array of exit codes to ignore in to the #run method, rather than raising an exception when a non-0 exit code gets returned. Cleaned up the rest of the code in the cli.rb file.
…pen4 library now. STDOUT is already being silenced from the Backup::Logger thanks to POpen4. `2> /dev/null` caused the STDERR to be silenced when an exception occurred, so users had a hard time figuring out what the problem was. This has now been fixed.
…using relative paths and " ~ " for $HOME. This provides more flexibility in the backup configuration file, improves the readability of the code and makes the overall implementation more solid and the generated paths more consistent.
…the -P option caused file transfer issues.
…repare! and #log! methods from #initialize and #perform! in to the Backup::Database::Base class in the #perform! super-method. Now, instead of running #prepare! and #log! from within the child (Database) class, we invoke it from the Backup::Database::Base class by calling #super in the child (Database) class's #perform! method. This cleans up / refactors / abstracts code, and also fixes the WILDCARD triggering issue.
… as a base (always required) gem through the gem spec when Backup is installed.
…le @@compressor of Backup::Model).
Need to make sure the shell knows about exceptions / problems.
… optional dependency list. Fixed the issue where the CLI would never load if popen4 wasn't installed and simply error out providing vague exceptions. If either Thor or POpen4 aren't installed, the CLI will provide commands in order to properly install them.
… (Also updated the whole GitHub wiki at this time.)