nitro

This is a great post, and you captured really well what makes Void so unique and lovely to engage with. Despite packaging being so high quality, it's great that there's still improvements to be had. I would be really interested to know more about: 1. What apk solved more specifically that xbps couldn't. You mentioned dependency resolution, is it just that it makes virtual dependencies a stronger default? 2. This is completely tangential, but choices to use dinit and musl. Admittedly the use of musl is why I've not given chimera more time: I'm paranoid that I'll need some Linux binary to function in society (e.g. zoom) and I'll hit a wall. Runit is really neat, but nitro really shows that there's capacity to improve significantly and I would love to know how dinit was chosen and your thinking there. 3. Did you think much about build flags, variants and even -git packages when designing your system? I do wish for a brave-bin out of curiosity, a neovim-git for practicality, etc. It's frustrating we don't have .NET packaged yet on Void, so no *arr stack. I'm wondering if Chimera is able to tackle these with its design! It's been really nice using turnstile as part of my setup and reinforcing that systemd-less can function really well!