OK. I give it up.
Have you done the test I've asked ? Reinstall GSX and the Uninstall it immediately. You'll see the GSX folder WILL be removed.
From my point of view GSX is bundled to tight with your Airport sceneries.
In reality is exactly the opposite: BEFORE we had all set of GSX/Couatl files included in the airport installers, because what we included was almost everything that makes GSX, except GSX specific animations like people, etc. This would have resulted in the GSX code being ALWAYS removed, because it was installed by every product, so every product uninstaller would remove it.
It's NOW (not for all installers, only the most recent ones, CYVR and JFK V2 are made like this) that we
unbundled from the airport installer, and simply suggested users to download and install GSX separately.
So, is exactly the opposite as you are thinking: when GSX was "bundled too tight" (in older installers), it was easier to uninstall, because any uninstaller had the chance to remove its folder, and when we
unbundled it, making it an OPTIONAL (although suggested) download, the ability for all products to be self-updated, makes it more difficult to uninstall because it's now a shared component, which means it would be wrong to have it uninstall it automatically, but it must be asked to the user, which is exactly why there's a question about its removal at the end.
I also will not update them
Again you are missing the point: whenever you run their installer, they'll self update anyway and guess what, the things that self update themselves, are exactly the Couatl/GSX code, and the Addon Manager.
But that's not the point. The point is WHY you wanted to get "rid of " GSX in the first place, and initially you make it sound as if there was some "problem" with it, with unjustified airport cache updates.
THEN, you said that it should be considered normal to keep update the Scenery Library, so this means YOU were triggering such cache updates, because this is how it's supposed to work. But of course, this reasoning doesn't have any grounds because, if you REALLY are updating your Scenery Library, as you said you are,
even the FSX own cache will update too!.
Which means, the "problem" of annoying cache updates because of frequent changes to the Scenery Library you wrongly attributed to GSX, would appear exactly the same by FSX itself so, using your reasoning, you should stop using FSX itself, because even FSX updates its cache each time you make a change to the Scenery Library, that's why it's wrong wanting to remove GSX *because* of that problem.
