2.0.0 Breaking Changes

[Elsie19]

Breaking changes

Pacstall will be releasing v2.0.0 Apricot within this week. We follow Semantic Versioning, and as such, the change from 1.7.3 -> 2.0.0 means that breaking changes have been introduced.
#608 and #543 introduce a better environment for Pacscripts to be executed in. These changes will stop execution of the prepare, build, and install functions, if any command inside them fails, which will make sure that your package won't continue installing, which would break the build. These pull requests also prevent pipefails and missing variables, meaning that commands such as these:

cat /etc/os-release | grep "window_manager" | less # Fails due to `grep` failing to find `"window_manager"` string in the `cat` output
mkdir $notarealvariable # Fails because this variable was never created
ping 1111111.11111.111 # Fails because this is not a real IP address, and would result in a non 0 exit code

Will fail now, unlike before. If your Pacscripts are properly configured, this will not affect you in any way, but if your Pacscripts rely on potentially missing variables or piping in an unstable way, you should take steps to fix those before the release of 2.0.0.

CC: @pacstall/pacscript-maintainers