The new APT 3.0 solver

Re:The new APT 3.0 solver by miki123211 on Tuesday May 14, 2024 @08:30PM (#40361725)

The even healthier choice is to store all your system state in a config, you can then just occasionally clean up the config. This also lets you put extensive comments on why a package is needed or even create a submodule for a specific project.

Shame that the only bistro that lets you do this is extremely arcane and difficult to learn if you do not have a PhD in mathematics.

[ Parent | on HN ]

Re:The new APT 3.0 solver by pxc on Tuesday May 14, 2024 @09:19PM (#40362069)

> Shame that the only distro that lets you do this is extremely arcane and difficult to learn if you do not have a PhD in mathematics.

Hey, there are two! Remember GuixSD

[ Parent | on HN ]

Re:The new APT 3.0 solver by anthk on Wednesday May 15, 2024 @11:43AM (#40368428)

Guix is not that difficult.

[ Parent | on HN ]

Re:The new APT 3.0 solver by pxc on Wednesday May 15, 2024 @03:42PM (#40371435)

I don't think NixOS is either, but I figured I'd let a shitposter have their hyperbole. :)

I don't begrudge any Guix contributors protesting that the GuixSD docs are undersold by such hyperbole, though! If that's you, carry on. :D

[ Parent | on HN ]

Re:The new APT 3.0 solver by curt15 on Wednesday May 15, 2024 @06:29AM (#40365102)

Is the mapping from config -> state reproducible? Traditional distros drift over time with lots of upgrades because the state is not just a pure function of the set of packages to be installed (the "config"). It could depend on the system's history, such what packages were installed or removed in the past.

The so-called "atomic" distros don't attempt to make the (config -> state) transformation reproducible but rather sidestep the problem by snapshotting and replicating the output of the transformation -- the files on disk after various installs, upgrades, and config changes.

[ Parent | on HN ]