void-packages

Just a reminder that it doesn't have to be this way, and the Debian problem is mostly self-inflicted and caused by decades of backwards compatibility. You don't have to suffer it if you control what's running on your machines. Let's see how btop (mentioned in the article) is packaged by other distributions. Alpine: one very transparent and easy to understand shell script with about 20 LOC: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/c... Arch: same thing (there are a couple more files there, one of them is for an optional new version checker, the other is automatically generated): https://gitlab.archlinux.org/archlinux/packaging/packages/bt... Void Linux: unlike the previous two, this uses a declarative language; it's still very short and easy to understand (though I prefer the imperative approach): https://github.com/void-

I'm using void. https://github.com/void-linux/void-packages/issues/26415 gives an insight, though it doesn't explain the whole problem, if I remember correctly what maintainers wrote elsewhere. > ROCm is a train wreck to compile from source but can be done with sufficient bloodymindedness. Yeah, I did that myself. Not impossible, just a bit annoying and time consuming. The issue I ran into then was exactly picking the gpu model (incredible that this is even necessary) and not having the gfx1032 available, see https://github.com/void-linux/void-packages/issues/26415#iss... for what I was following back then. I tried to edit the configuration for the gfx1032 anyway, but it did not succeed. Side note: Already having to know which card corresponds to which code is annoying, and completely unnecessary. They could also just map the consumer fac

kinda. https://github.com/void-linux/void-packages/