v2.1.1

This is a small update that adds a few QoL features in addition to a change in the default encryption method, which fixes a previously unnoticed permissions bug. The change will simply require a rerun of backups in order to start using the newly-applied encryption method.

• Added a BACKUP_ERROR_HANDLING configurable variable, which lets users configure how they want the script to handle backups when errors are encountered. The default will have the script prompt the user with options, which was the same as previous 2.x.x versions. Further documentation for interested users can be found in the CONFIGURABLE VARIABLES section inside linux-autosetup.sh.
• Fix a permissions issue with ~/.gnupg requiring root permissions due to the script being run as root. Please also check your own gnupg directory in case this problem has affected you. Decided this might also be a good time to look for a different encryption tool, and so the script now uses openssl by default to perform archive encryptions, which does not have these side effects... as far as I know.
• Archives that have failed to be backed up for some reason (probably mainly from incorrectly inputting encryption passphrases) will now prompt the user if they want to try again. This can be controlled by BACKUP_ERROR_HANDLING.
• tar will not be verbose by default anymore due to an oddity with its output messing with the encryption prompt for the passphrase, which gets buried in text and can make it confusing to realize an input is required. Users that still want this verbosity can enable it by adding the v option wherever desired in their own custom event functions.

Packages from now on will now also include the sample configuration files found here.

v2.0.0

yay!

This update adds and changes a lot of stuff, which introduces some breakages from v1.x.x warranting a bump to v2.0.0. This update also comes with some neatly prepared documentation found on the new wiki and implemented help functions users can use in the script.

CHANGELOG:

• Added archiving! Archives offer a method of copying, compressing, and encrypting files, with easy-to-modify event functions if users feel that they would prefer e.g a different compression or encryption method.
• Added option-handling. A user can now technically perform an autosetup with a single command without any input if they know what they want to do beforehand.
• Major overhaul to the autosetup CLI. The user is now given more easily accessible tools to set up entries for the autosetup, which offer more information and are (hopefully) more intuitive to use. Additionally, help functions have finally been expanded on and are available wherever necessary for the user in the case that they do not understand what kind of input they need to give.
• Reveal an APP_INSTALL_BACKUPS configurable variable which lets the user specify autofilling/prompting for installing backups ahead of time.
• Backups will now be performed in a temporary directory TMP_DIR (defaults to "/tmp/linux-autosetup") before any old backups are dumped and replaced with the new ones, only and only if the backup command succeeded.
• Users are now prompted to resolve missing backup sources - currently there is no way to disable this, partly because I figured backing up a bunch of stuff only to find that something wasn't backed up and included is more annoying than an inconvinient prompt and also because I'm still deciding on how to make this properly configurable.
• Renamed app event functions to make more sense.
• bug will be squash

On the backend:

• Modularized functions into different files, which makes it easier to find functions while decluttering the main script.
• Hopefully improve maintainability of the autosetup CLI code, which should make adding features a lot easier.

v2.0.0-rc-2

Second attempt to achieve fully stable and usable v2.0.0.

• Fixed: #33 and #34
• Rewrote backup methods to more sensibly work together with dumping process. Backups and archives that are not completed yet will not disturb present backups/archives anymore until they have successfully completed - only then will the current ones be dumped and replaced.
• Adjusted installation order of archives and apps. Backing up will do apps first, then archives, while installing will do archives first, then apps. Currently unsure about what implication this has on flexibility, but changes will probably come in another update if this setup is not good enough.

v2.0.0-rc-1

Lots o' changes.

Mark testing point for pre-release of v2.0.0.

Documentation has been pretty much finished.

Changelog will come with v2.0.0 but gist is:

• archives
• overhaul of autosetup CLI
• option-handling is a thing now with running script
• bunch of other small things, probably

[broken] v1.1.0-beta

[edit]: this pre-release has a few bugs that are break-worthy enough for me to slap a "don't install pls" label on it. lots of stuff are being changed (again) due to current limitations, more than i expected making this take longer than also expected. because of all the difference, this release cycle's being scrapped with the next planned release(s) being v1.3.0-beta -> v1.4.0. soontm

Pre-release for what will become v1.2.0. Pretty much all the functionalities have been taken care of; polishing of things like outputs from the script (currently inconsistent, e.g. line breaks in some functions but not in others) and error handling will be the focus of the next release.

Changelog:

• Rehaul to the autosetup system.
  • Rather than enter an immediate strict "autosetup stage" and be prompted for options, users are instead directed to a command line which is essentially just a Bash terminal with the script initializing its functions. The user can then call one of currently four autosetup functions in order to initialize a setup. The main reasons for this rehaul was to make the code easier to maintain and add to, as well as allow more paths to abstraction implementations in the future. This also lets the user quickly make direct calls to install or backup functions if they prefer to do this instead.
• Archiving! Users can make use of archives, which allow for straight copying, compressing, or encrypting files. These come in 6 predefined but easily configurable functions that the user can modify if they e.g. don't like the compression method or want to use a different type of encryption. Documentation on this coming soontm.
• Bug-squashing grind never stops.

v1.0.0

First release of Linux-autosetup!