Skip to content

Conversation

@dmadisetti
Copy link
Contributor

I mentioned nix on discord- but this is the flake I've been using. Note the magic of nix is that you could pin nixpkgs to a release or commit and running nix develop on any computer will give, verifiably, the same environment and same binaries.

Obviously no pressure to merge this in. I just think it's nice to have the option.

@djungelorm
Copy link
Member

Thanks, I'll try it out.

I think this might be very useful in some of the other repositories (where there are many more non-bazel dependencies).

Would also be good to add a job to the CI to test that it works.

@dmadisetti
Copy link
Contributor Author

Super long build time since nix builds Bazel from scratch (the wrapper causes the hash to change triggering a rebuild). I think there might be a way around it (defining a new Bazel, opposed to modifying an old one), but this would also go away with a nix cache.

The validity of the definition (nix check flake) only takes a few seconds though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants