Linux Users
Please note that we have depreciated the Fedora COPR, Arch AUR, and Debian repos for GridTracker v2. GridTracker v2 is not a simple update to GridTracker v1 but is a completely new program, installed in its own location different from v1. As GridTracker v1 is now EOL and out of support; we have taken the repos down for v1 and will not be supporting new installs
Please do not uninstall v1 until after v2 is installed and running as we'll pull the settings from your old version if it's v1.24.0908 or v1.24.0922.
So why are we doing away with the repos?
With v1 we relied on users to see that there was an update and use your package manager (or you manually) to download and install the update. In v2 we have a built-in feature that allows GridTracker to see if there is a new version and download it and let you know. Then on exit, the updater will prompt you to allow the updater to update GridTracker with that new version. So for most users, you would only ever have to download the first installer and allow GridTracker to keep you up to date.
But wait, how does it do that without breaking RPM/DPKG?
The updater is designed to work with your OS's package manager - It downloads and installs an updated package (.deb, .rpm, or whatever your system uses) and upgrades using the system package manager (rpm or dpkg) behind the scenes to update GridTracker.
But what if I don't want to update?
Well, you can just not enter your credentials to allow the update when asked. But at some point there will be breaking changes or a new feature you do want and because we use a rolling/progressive development style with somewhat frequent small updates and changes that will result in something that could be a mess. Users that are updating now from pre-v1.24.09xx versions are finding that out right now with their settings not translating to the new version at all.
So if you choose to not update to a particular version right away that's your choice, but we hope you do choose to update and stay current. If you come to us saying something needs to be fixed and it's already been fixed in the version you skipped, you'll probably get the expected response.
