The 1.x iteration of globalprotect-openconnect is no longer being
developed. Remove related components from nixpkgs.
Signed-off-by: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Currently, every platform uses LLVM 18 except for the following
exceptions:
* Darwin, on LLVM 16.
* WASM, on LLVM 16.
* Android, on LLVM 12.
As discussed with RossComputerGuy and alyssais on Matrix, we plan to
bump both Darwin and Linux to LLVM 19 after the 24.11 branch‐off,
and try to keep them in sync after that, bumping to new stable LLVM
releases immediately after releases branch off.
This prepares for a 25.05 where `llvmPackages` is a simple
platform‐independent alias by removing all the redundant branches
and upgrading WASM and Android to LLVM 18.
I checked with lilyinstarlight who did the previous LLVM bump for
WASM and she confirmed that there should be no particular reason to
keep it pinned to 16 so long as Firefox continues to compile, and I
have confirmed that it does.
Android was last bumped back when the other platforms
were on LLVM 7, which is pretty good evidence that these
platform‐specific conditionals create unnecessary divergence
and bitrot quickly. Due to the “maximum‐of‐minimums”
cross‐compilation logic, it was inevitably picking LLVM 16 or 18
anyway. `pkgsCross.aarch64-android.hello` fails the exact same way
as it does on `master` on all the platforms I tested (compiler-rt
failing to build on `aarch64-linux` and `x86_64-linux`, and the Linux
headers package expecting `gcc(1)` on `aarch64-darwin`).
I’m not entirely sure that the maximum‐of‐minimums logic is
correct (should it be completely ignoring `buildPlatform` like this?),
but since it will hopefully go away very soon I’ve decided not to
spend more time thinking about it.
