You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure adding an uninstall script option is as easy as it sounds.
Currently, the peaclock binary is the only file that gets installed. The binary file can be removed by retrieving its path using which peaclock, followed by its removal using rm /path/to/peaclock.
The config directory is explicitly created by the user in the location of their choice, therefore, I think it should only be explicitly removed be the user.
The best method would be to use a proper distro package manager to handle install and uninstall, such as pacman on Arch Linux. Programs such as stow are also useful for easy uninstalls. The install script could perhaps write to a separate file and store a list of installed files that could then be referenced in an uninstall script. Although, the file would have to exist somewhere on the system until needed, and there's no guarentee that the stored paths haven't changed.
While I currently think the lifetime of a program is a job best left for a package manager, I'm open to any ideas or implementation suggestions.
Please add and document and uninstall option in the RUNME.sh script (option) and README.md (documentation)
The text was updated successfully, but these errors were encountered: