Certainly not FPC, because the hard dependency on GTK2 was a misunderstanding.
For Lazarus it seems like dependency on GTK2 is considered a bug and not a fundamental incompatibility, because there are too many GTK2 applications to completely remove it from Debian.
I don't like it either, but that's not the direction I would go. I haven't looked into Arch yet in enough detail to have an informed opinion, but maybe I should.
PD: Guix can do the same as fbsd and nbsd because, well, setting up an isolated environment with time-bound tools it's basically what Guix was born for, reproducibility. Scientific repo for a paper must be run point to point as we had a Slackware setup with Slackbuilds in 2007? That's the point of Guix. You would say... docker. But docker it's overkill.
"Debian GNOME team announces intent to remove GTK 2 in Debian 14" (08.01.2026)
https://news.ycombinator.com/item?id=46548257
P.S. Still hope GNOME maintainers let other volunteers maintain GTK 2.
They already said this is fine: https://lists.debian.org/debian-devel/2026/01/msg00146.html
Recently I wish Debian was more Debian.
> That being said I would not object if someone wants to take over the maintenance of GTK2, though I believe keeping it for beyond duke is beating a dead horse.
Source: https://lists.debian.org/debian-devel/2026/01/msg00146.html
The Nix or Guix package managers are likely your easiest bet. See
https://nixos.wiki/wiki/Lazarus
https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...
The harder part is to upgrade Lazarus to qt6. Until that happens, Lazarus needs to be shipped as snap, flatpack or appimage with the gtk2 so's.
Exactly. "Let me explain how some else needs to do this thing, and how easy it is, and how that someone else needs to get right on that for my convenience". Because you're here to condescend, not to actually do anything.
?
- Hexchat IRC client is another popular application that is still stuck with GTK2.