FlakeHub brings a crates.io-like experience to Nix and flakes, with semver releases and publish-time checks to make sure the flake is easily distributable.
Check it out, let us know what you think! I'll be here answering questions all day.
FlakeHub brings a crates.io-like experience to Nix and flakes, with semver releases and publish-time checks to make sure the flake is easily distributable.
Check it out, let us know what you think! I'll be here answering questions all day.
You can search on the web UI, though: https://flakehub.com/search
So shouldn't flakehub be owned by The NixOS Foundation instead of being a 3rd party and proprietary? It seems to be a critical feature for flakes.
I know that pre-flakes conventions for reusing Nix code are pretty open-ended, and naturally 'pure evaluation mode' means turning a bunch of things off. I can also see how if you are interested in integrations with stateful systems or maybe relaxing certain constraints or allowing/tracking some 'impurities', that might also seem like a step in the wrong direction.
Do you have any possibilities (or examples) in mind for how Nix might be used beyond the 'local optimum' of most current usage?
Yeah I'm not sure what would be best in this regard. Flakes are on track to becoming a critical feature for Nix, though I'm not sure Flakehub will be a critical feature for Flakes. It seems there are some issues with standardization of pinning and versioning that need to be fixed in upstream, but the Flakehub folks seem committed to transitioning to those when fixed:
https://discourse.nixos.org/t/introducing-flakehub/32044/14
As long as those standards get worked out upstream and Flakehub and similar projects follow them, and they're technically interchangeable, then they may be ok. It's if there are a bunch of different proprietary solutions with different proprietary standards where it becomes problematic.