This script might be a bit over-complicated for its purpose, but I enjoyed creating it. It can install and update Pulse on any Linux distribution, as long as you have GNU versions of awk, bash, curl, and grep.
In addition to adding the script, this PR also updates the README with:
Multiple instructions on how to get the project running on Linux.
A fixed "License" heading (a subtle change not worth a separate PR).
It might also be worthwhile to add a simple way to uninstall everything related to Pulse. This is something I may address in a future PR.
Part of the script relies on the -v flag, which I added in the PR #116, so the script is able to update the binary if we're running an outdated version.
The script currently lacks a method to accurately determine the installed version of Pulse. As a result, during the update to the next release, users will see the Could not determine the current version of pulse. Assuming update is needed. message.
Moving forward, starting from the subsequent release where version tracking is implemented, updates will display the Updating pulse from ${current_version} to ${latest_version} message when updating from that release onwards, which is actually informative.
This script might be a bit over-complicated for its purpose, but I enjoyed creating it. It can install and update Pulse on any Linux distribution, as long as you have GNU versions of
awk
,bash
,curl
, andgrep
.In addition to adding the script, this PR also updates the README with:
It might also be worthwhile to add a simple way to uninstall everything related to Pulse. This is something I may address in a future PR.
Part of the script relies on the
-v
flag, which I added in the PR #116, so the script is able to update the binary if we're running an outdated version.The script currently lacks a method to accurately determine the installed version of Pulse. As a result, during the update to the next release, users will see the
Could not determine the current version of pulse. Assuming update is needed.
message.Moving forward, starting from the subsequent release where version tracking is implemented, updates will display the
Updating pulse from ${current_version} to ${latest_version}
message when updating from that release onwards, which is actually informative.