as a user, I would appreciate it if Arch Linux were to switch to statically-linked haskell packages. Maybe there's a good reason not to do this, but to me, it looks like it would be an advantage if it were implemented.
Honestly it's really annoying having to upgrade numerous bunch of haskell deps that only two pkgs rely on, but I do believe Arch doesn't do static compiling for security reasons.
On 6/26/26 11:28 AM, Erwin Iosef wrote:
as a user, I would appreciate it if Arch Linux were to switch to statically-linked haskell packages. Maybe there's a good reason not to
Haskell is one of those 'fun' topics. Its interesting to compare how other distros deal handle this. Not an expert on this but looks like debian / ubuntu went the fully static route while fedora keeps a "core" set of shared libraries. Both approaches avoid the surging package update storm. shared lib advantage -------------------- Unless there are a lot of haskell apps being used at the same time, the shared lib benefits may quite negligible. Disk space estimate ------------------- may or may not be too accurate (thank you google): Approx Disk Space Used (MB) shellcheck plus Distro shellcheck pandoc Num Packages ======= ========== ====== ============ Debian / Ubuntu 23 80 2 Fedora 45 120 5 Arch 200 1000 150 In my case these were the only 2 haskell based applications: (1) pandoc I chose to remove pandoc and all it's haskell deps. I use sphinx for my own stuff have no need for it. This got rid of the majority of haskell packages but not all. (2) shellcheck Drags in a smaller group of haskell packages. I occasionally use this, but may remove this as well. Quite useful if writing bash scripts. I tend to program in C and python for the most part so my own need is minimal. Thanks to all for bringing it up. gene
participants (2)
-
Erwin Iosef
-
Genes Lists