-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VoidLinux Support? #88
Comments
On the master branch, things related to package management and owned files are mostly hardcoded to pacman. Arch derivates thus work OK. At one point, I tried to refactor things in order to add support for apt and Debian. The reason why things didn't go anywhere is the massive amount of clutter a Debian filesystem has - there are tons and tons of auto-generated configuration files and other forms of mutable state, such that a third-party tool such as aconfmgr would find very difficult to know which package owns such files, assert whether they contain what they're supposed to contain, or the exact conditions for whether they should be present on the filesystem or not. I don't know much about Void Linux. If its philosophy about overall system complexity is closer to Arch than Debian, then perhaps adding support for it would be feasible. Another requirement would be that its package management design still holds the same general concepts, such as whether a package was installed automatically or explicitly requested by the user ("pinned" packages), and support for operations used by aconfmgr (such as searching for files owned by packages but modified since the package was installed). Debian/apt incidentally did mostly match here, with the biggest discrepancy being that Debian supports installing the same package twice with different architectures, whereas on Arch that would have to be two distinct packages. |
@CyberShadow - Great. I don't use Debian-like distros for those reasons you mentioned anyway. The biggest difference between Arch & Void is the init system - but I don't know what the biggest difference from aconfmgr's perspective is. |
|
Thanks; sorry for repeating bad information. |
Does anyone know of an implementation for APT package managers? |
I have not used aconfmgr yet (planning to test it soon), but I am using pacdef for declarative package management. pacdef has an apt backend which I have not yet tested, and other backends could be added though I don’t know the level of effort involved. |
(Just an FYI I recently switched to nixos and this solved all my problems (I talked about my experience |
Great video. I am also (very slowly) moving to Nix (and, probably eventually, NixOS). |
I just ended up using ZFS snapshots + void. NixOS actually increases complexity and is not worth it in the long run (in my opinion, of course). |
How hard would it be to support VoidLinux? Has anyone tried it?
Thanks :)
The text was updated successfully, but these errors were encountered: