The Guix Nix Abomination: Leveraging Guix derivations in Nix
24 points by Hasnep
24 points by Hasnep
See also: Guix's Nix service.
unfortunately, this seems to use a separate store? would be cool to have guix and nix coexisting in the same store and possibly sharing some derivation (would probably convince me to switch to guix)
It’s cool that this is possible, but is there any practical use? My impression was that Guix was the (much) smaller community compared to Nix, so probably not many Nix users would need to reach for Guix recipes?
Guix contains a full source bootstrap. It would be nice for Nix users to benefit from that without having to recreate it all themselves (though practically I doubt nixpkgs would want to depend on guix).
It also demonstrates that changing source languages is feasible, possibly encouraging or validating the potential for nixlang-alternatives that integrate with nixpkgs/nix-store.
For the guix community, they might appreciate the option to use nix tooling (e.g. the variety of cache/store implementations).
More generally, I think the store concept used by Nix and Guix is one of its strongest, and it would be good to see this shared/reused/standardised across projects, and this shows it might not be that hard.
That's interesting, I'm currently migrating from nix to guix. I have started contributing to the guix repo and maintaining packages involves a bit of work from the community.
I wonder if we could get to a world where we have standard, universal derivations. The user could then use their favorite builder on top of it, whether it's Guix, Nix or something else.
This would split the maintenance of packages across multiple distros.
I guess the downside is that you lose control over the ecosystem.