coq-nix-toolbox
coq-nix-toolbox copied to clipboard
coq-community
Nix helper scripts to automate local builds and CI [maintainers=@CohenCyril,@Zimmi48]
IIUC the diagnosis in coq-community/lemma-overloading#68, `buildInputs` is pretty useless because it is only used in the derivation that is built by `nix-build` called without arguments. It doesn't affect the derivation...
Maybe this should be a config option so that projects whose main contributors all use the same system (Linux or macOS) do not actually duplicate the jobs they run?
It feels like we are growing out of a README-based documentation. I think we could apply the principles advocated in the Diátaxis framework (https://diataxis.fr/): split documentation into tutorials, how-to guides,...
From the documentation in `config.nix`, it would seem that `nix-build` and `nix-shell` (without arguments) should target a different attribute if `attribute` and `shell-attribute` are both set and differ. Yet, (at...
For instance, for Coq, we would need tools like `jq` and `git` to make some dev scripts work.
It happens that my package is in nix already, so I picked the non short name of the package. But from the README is not so clear what one should...
This is dirty! https://github.com/coq-community/coq-nix-toolbox/blob/5e713b1b2be756cd5d9b6df6615390e772ff1dfb/.nix/shellHook.sh#L204-L205
We could consider having `generateNixDefault` print in the console that the next step is to run `nix-shell --run "initNixConfig YOURPACKAGENAME"` when the `config.yml` file does not exist yet. And `initNixConfig`...
https://github.com/coq-community/coq-nix-toolbox/blob/ab43447ff01c2ccf712f14aca5b99d14e5735440/.nix/shellHook.sh#L154 One way to do it is to pass only the selection, via task cf #7
https://github.com/coq-community/coq-nix-toolbox/blob/b1e5c52bdc1d79b7cd220476ebd9bc552a2331c7/project-default.nix#L1
Metadata
Owner
Metadata
Nix helper scripts to automate local builds and CI [maintainers=@CohenCyril,@Zimmi48]