You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As much as we can, including Arch/AUR packages and even some configuration files.
Benefit?
Ability to deploy across almost all linux distros.
P.S. You are able to use guix on NixOS, or use nix on GuixOS.
Enhance stability and flexibility. Such packaging method allows multiple versions exist at same time, which makes dreams like [Feature] Revive old configs #1059 possible.
Accelerate installation speed once we provide pre-built packages in guix (or nix).
Of course we do not need both of them. So, which one?
What is guix?
It's a cross-distro package manager, similar to nix (actually "guix" means nix written in guile) but easier to learn (?). Its configuration language, Guile, is a general programming language for many things, comparing to nixlang which is only suitable for nixos thingy.
I'm trying to use Nix on Arch. But the installation process of Nix itself on non-NixOS distros is a mess and not idempotent at all. You'd better have a Btrfs snapshot before ever install it, whether you install it by using pacman or Nix official shell script.
To solve this we may need a better installation script for Nix itself.
Using Guix?
I've tried Guix before. I didn't remember but Guix itself seems to be easily installed. However when adding Guix channel, its updating speed is too slow and I don't know what is wrong. Probably needs a powerful machine, which is not acceptable for this project.
Still, there may be solutions, such as custom guix channel which contains only a few packages for this repo to guarantee performance.
What to "repack"?
As much as we can, including Arch/AUR packages and even some configuration files.
Benefit?
Steps to achieve
The text was updated successfully, but these errors were encountered: