Ability to use non-default `devShell` #31

New issue

Open

opened 2022-02-07 17:14:44 +00:00 by sir4ur0n · 2 comments

sir4ur0n commented

2022-02-07 17:14:44 +00:00

(Migrated from github.com)

Current implementation hard-codes the use of devShell.${system} while other shells can be provided in flake.nix at devShell.${system}.<whatever>, e.g. devShell.${system}.foo.

It would be useful to provide means of accessing these other shells too.

[Current implementation](https://github.com/edolstra/flake-compat/blob/master/default.nix#L196) hard-codes the use of `devShell.${system}` while other shells can be provided in `flake.nix` at `devShell.${system}.<whatever>`, e.g. `devShell.${system}.foo`. It would be useful to provide means of accessing these other shells too.

adrian-gierakowski commented

2023-02-18 14:35:57 +00:00

(Migrated from github.com)

this could be solved generically the solution proposed here

this could be solved generically the solution proposed [here](https://github.com/edolstra/flake-compat/issues/51)

adrian-gierakowski commented

2023-02-18 15:36:45 +00:00

(Migrated from github.com)

actually, you can actually do that with:

resultOfFlakeCompat.defaultNix.devShells.${system}.foo

you can accept any outputs of the flake this way, see here

actually, you can actually do that with: ```nix resultOfFlakeCompat.defaultNix.devShells.${system}.foo ``` you can accept any outputs of the flake this way, see [here](https://github.com/edolstra/flake-compat/issues/51#issuecomment-1435701321)