4 ms·
Alpine has come cool perk: When a Nix user is flexing about declarative package management, live-edit your /etc/apk/world and run `apk fix` to show them how to
by blueflow 3y ago
Alpine has come cool perk: When a Nix user is flexing about declarative package management, live-edit your /etc/apk/world and run `apk fix` to show them how to do it without Nix.
- mbrock 3y agoI can reinstall Alpine from scratch in around the time it takes Nix to evaluate my system flake
- lambdaba 3y agoThat's cool but Nix/OS does much more than declarative package installs.
- intelVISA 3y agomy fave Nix feature is telling people I use it
- MaKey 3y agoThe new "I use Arch btw".
- vaylian 3y agoI use the nix package manager on Arch btw
- aodonnell2536 3y agoArguably the original one, too.
- cqqxo4zV46cp 3y agoIf it were easier to use, it wouldn’t be as big a flex. So we can’t be having that!
- orbat 3y ago"It may be slow, but it's hard to use!"
- justinclift 3y ago[flagged]
- robertlagrant 3y agoIf you have to ask, then no.
- justinclift 3y agoGood point. :D
- intelVISA 3y agoI'm not :(
- justinclift 3y agoClearly, as I had to ask. :)
- mid-kid 3y agoI generally prefer Gentoo's method: /var/lib/portage/world for manually installed packages, /var/lib/portage/world_sets for selected sets, and sets can be defined in /etc/portage/sets/. This allows you to split your packages into categories and only install certain bits on systems where you need them, as well as add any comments to the files as necessary. The equivalent to `apk fix` is `emerge -uDU @world && emerge -c` which is slightly more unwieldy but oh well. Alpine allows something akin to sets by using `apk add -t setname pkg1 pkg2 pkg3`, which creates a dummy package which depends on your package selection. I generally create shell scripts in /etc/apk/sets/ to mimick the Gentoo experience, but it's not always the same.