Just like for SADX, this is a simple program (originally made by @MainMemory ) that allows the user to choose whether to install the new Manager or the legacy build of the old manager with update support removed.
This version checks if the new Manager already exists and ask the user if they want to install the last update to avoid duplicate. Note that they can still choose to have it twice regardless, but this shouldn't be an issue since the Manager has a profile and mutex system that prevent multiple instances.
Before merging:
Double check if the Build Script is correct, I did that based on the SADX version
Making a snapshot and release of the legacy branch would be nice.
Whenever this is merged, we can ask a few people to test if everything works before making a global announcement on Discord, in case it needs an emergency fix, it shouldn't, but better be safe than sorry.
Just like for SADX, this is a simple program (originally made by @MainMemory ) that allows the user to choose whether to install the new Manager or the legacy build of the old manager with update support removed.
This version checks if the new Manager already exists and ask the user if they want to install the last update to avoid duplicate. Note that they can still choose to have it twice regardless, but this shouldn't be an issue since the Manager has a profile and mutex system that prevent multiple instances.
Before merging:
Whenever this is merged, we can ask a few people to test if everything works before making a global announcement on Discord, in case it needs an emergency fix, it shouldn't, but better be safe than sorry.