Skip to content
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

Open
dm17 opened this issue Nov 8, 2020 · 9 comments
Open

VoidLinux Support? #88

dm17 opened this issue Nov 8, 2020 · 9 comments

Comments

@dm17
Copy link

dm17 commented Nov 8, 2020

How hard would it be to support VoidLinux? Has anyone tried it?
Thanks :)

@CyberShadow
Copy link
Owner

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.

@dm17
Copy link
Author

dm17 commented Nov 8, 2020

@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.

@The-Compiler
Copy link

Void's pkg manager is based on Arch's

It's not, FWIW:

The X Binary Package System (in short XBPS) is a binary package system designed and implemented from scratch.

@dm17
Copy link
Author

dm17 commented Nov 8, 2020

Void's pkg manager is based on Arch's

It's not, FWIW:

The X Binary Package System (in short XBPS) is a binary package system designed and implemented from scratch.

Thanks; sorry for repeating bad information.

@0atman
Copy link

0atman commented Aug 1, 2021

Does anyone know of an implementation for APT package managers?

@star-szr
Copy link

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.

@0atman
Copy link

0atman commented Mar 24, 2024

(Just an FYI I recently switched to nixos and this solved all my problems (I talked about my experience
here) - this is a hard problem to solve on any system, and I'm impressed with @CyberShadow for tackling it on arch!)

@CyberShadow
Copy link
Owner

Great video.

I am also (very slowly) moving to Nix (and, probably eventually, NixOS).

@dm17
Copy link
Author

dm17 commented Mar 24, 2024

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).
Shall I close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants