Another feature is that you can git disect your whole system and spin VMs of your system deceleration file with one liners. So, combined, you can gradually remove unrelated packages and pin point the problematic package and commit without having any idea what they actually do and how they do it. Eventually you'll be posting a dozen lines deceleration file and a git hash saying "this package got slow in that commit" and there won't be any room for ambiguity.
Alone, this justifies abandoned every other package manager except for Alpine's and maybe Openwrt's that have low-RAM requirements that can't be met by Nix and Guix. But everything between Debian, Arch and RPM has really outlived its usefulness.
Announcement
Collapse
No announcement yet.
GNU Guix 1.0 System Distribution & Transactional Package Manager Released
Collapse
X
-
Originally posted by Michael_S View PostI have Guix running in a VM, it's nice.
That's the benefit of free software: if you don't like it, you're free to not use it or to fork it and make something you do like.
We can't win. Everything converges on one solution, like systemd, and you get people screaming that choice is being taken away. Everything diverges into dozens of choices, you get people screaming that there is so much wasteful duplication.
And as it turns out GuixSD uses the GNU Shepherd init system. It seems to work fine, though I haven't done anything mission-critical with it.
I guess it's just a symptom of linux being only a kernel.
- Likes 1
Leave a comment:
-
Originally posted by Venemo View PostSorry for my ignorance but what problems does Guix solve that isn't yet solved by other package managers?- Installing packages as user inside the home directory, on GuixSD/NixOS leveraging packages that are already installed system-wide
- Managing multiple versions of a package on one system
- Distribution of a package and its dependencies to other systems, in a way that is transparent to the package manager
- Can use binary package repositories, or build from source, or a combination of these
For example, if some snap/flatpak contains a bundled outdated and vulnerable library, that is a problem. And in many cases you have no way to tell even.
If however some guix/nix package depends on an outdated and vulnerable library, it will be visible to the package manager. The user can track which packages require the vulnerable version, they can patch and recompile the library (if feasible), and once the last dependent package is removed from the system, the vulnerable library can be automatically removed too.
- Likes 6
Leave a comment:
-
Originally posted by Venemo View PostSorry for my ignorance but what problems does Guix solve that isn't yet solved by other package managers?
The relatively uncommon thing that Nix and Guix should give you is atomic transactions. Rolling back to previous versions should always work and be almost instant, since it just involves changing a few symlinks.
The unique thing they give you is bit-for-bit reproducible builds. I don't think they have it working for all packages, but for many software packages if you built libfoo version 3.4.5 for x86_64 on Guix anywhere it should be bit-for-bit identical to everyone else's build of libfoo version 3.4.5 for x86_64. Likewise the same is true for Nix, though I don't know if the same version built on Nix and Guix would be identical. That kind of reliably reproducible thing is huge.
The Debian project, among others, has work ongoing about reproducible builds but as far as I know - and I could be wrong - they haven't made as much progress as the Nix and Guix teams.
Guix and Nix are also good for devops stuff. If you want two Ubuntu Linux VMs with complex configuration to be identical, you need to clone one to the other or do some work with other tools that automate the steps you need with files under /etc/ and the apt and deb tools for you (Chef, Puppet, Ansible, Saltstack, Sparrowdo, etc...) With Guix and Nix, the whole system configuration - packages, users, service settings, etc... - is managed by the configuration file for your package manager. So if you want a copy of a Guix installation you just copy the config.scm file from the source machine to the other Guix machine and then run "guix system reconfigure" and when you're done the two boxes are identical.
- Likes 6
Leave a comment:
-
Sorry for my ignorance but what problems does Guix solve that isn't yet solved by other package managers?
- Likes 3
Leave a comment:
-
Nice. Congratulations on the 1.0 release.
Guix (and Nix) can be installed on any distro, including Android. I used it to install xWayland, IceCat, and some other goodies on SailfishOS.
- Likes 2
Leave a comment:
-
Originally posted by Bsdisbetter View PostJust what the world needs: more package managers.
But guix (and nix) have solved the problem of package management. These package managers even cover what snap/flatpak are trying to achieve, in a much more elegant way.
- Likes 1
Leave a comment:
-
Sweet; time to set-up a VM with it.
Just what the world needs: more package managers.
- Likes 6
Leave a comment:
Leave a comment: