In reply to @edrex:matrix.org
on the other, they are, in practical terms, largely irrelevant with nixFlakes

In reply to @edrex:matrix.org
i gather it does some install-time introspection on your system to figure out what graphics drivers you are using

In reply to @tomberek:matrix.org
Understood, flakes are not completely done, nor have they moved out of experimental status. So you are in a bit of an awkward moment. I would like to re-do "nix pills" with flakes and nix2.4 cli at some point.

In reply to @balsoft:balsoft.ru
And perhaps add an auto-detector thing that would work similar to nixos-generate-config --show-hardware-configuration

In reply to @aciceri:nixos.dev
Hi!
Someone here knows a way to run nix flake check excluding some outputs? I would like to specify the excluded outputs directly in the cli.
The reason is that I want to be able to run that command on my machine which supports cross compilation but I want to exclude that outputs that need it when I run the command in a github workflow (where cross compilation is not supported and where I can't have an aarch64 host).

In reply to @niksnut:matrix.org
Currently there isn't. I guess we could add an --exclude flag or something like that...

Maybe balsoft's solution is better since the only use case that comes to my mind is when the host's architecture is different, but I don't feel like I can express an opinion.

Any quick workaround to do what I'm trying to do instead? Maybe a sequence of nix check where I manually specifying what want to check?

In reply to @aciceri:nixos.dev

Maybe balsoft's solution is better since the only use case that comes to my mind is when the host's architecture is different, but I don't feel like I can express an opinion.

Any quick workaround to do what I'm trying to do instead? Maybe a sequence of nix check where I manually specifying what want to check?

I'm trying to write a flake with the configurations of all my machines (using devos as template), included an aarch64 notebook. The problem is that when I run in the Github workflow nix flake check it tells me that "a 'aarch64-linux' with features {} is required to build blah blah..." and it stops.

Before adding the arm machine the workflow correctly worked.

The alternative would be to run several times nix build .#checks.x86_64-linux.<myCheck> with all the needed <myCheck>s. I see two problems:

• The number of my checks could grow in time and I don't want to manually add these lines in the workflow yaml, is there a way to get a flake's outputs? Then with a little bit of shell fu I could obtain the correct nix build command to run.
• According to the doc flake check not only builds the checks but also does checks that the flake's outputs are app definitions, nixos modules, overlays, etc... So it would'n be equivalent to just run a sequence of nix build

The alternative would be to run several times nix build .#checks.x86_64-linux.<myCheck> with all the needed <myCheck>s. I see two problems:

• The number of my checks could grow in time and I don't want to manually add these lines in the workflow yaml, is there a way to get a flake's outputs? Then with a little bit of shell fu I could obtain the correct nix build command to run.
• According to the doc flake check not only builds the checks but also does checks that the flake's outputs are app definitions, nixos modules, overlays, etc... So it wouldn't be equivalent to just run a sequence of nix build

In reply to @aciceri:nixos.dev

The alternative would be to run several times nix build .#checks.x86_64-linux.<myCheck> with all the needed <myCheck>s. I see two problems:

• The number of my checks could grow in time and I don't want to manually add these lines in the workflow yaml, is there a way to get a flake's outputs? Then with a little bit of shell fu I could obtain the correct nix build command to run.
• According to the doc flake check not only builds the checks but also does checks that the flake's outputs are app definitions, nixos modules, overlays, etc... So it wouldn't be equivalent to just run a sequence of nix build

In reply to @aciceri:nixos.dev

The alternative would be to run several times nix build .#checks.x86_64-linux.<myCheck> with all the needed <myCheck>s. I see two problems:

• The number of my checks could grow in time and I don't want to manually add these lines in the workflow yaml, is there a way to get a flake's outputs? Then with a little bit of shell fu I could obtain the correct nix build command to run.
• According to the doc flake check not only builds the checks but also does checks that the flake's outputs are app definitions, nixos modules, overlays, etc... So it wouldn't be equivalent to just run a sequence of nix build

1. AFAIR you can generate workflow YAML's at runtime. If so, nothing is stopping you from using Nix to generate them with builtins.toJSON. If you want an example on how to do it for buildkite, see https://github.com/serokell/common-infra/blob/master/flake.nix#L69

In reply to @ilkecan:matrix.org
To get the flake outputs, there is nix flake show but it is for humans. Recently a PR that adds --json flag is merged but it seems this didn't hit the channels yet.

In reply to @balsoft:balsoft.ru

1. AFAIR you can generate workflow YAML's at runtime. If so, nothing is stopping you from using Nix to generate them with builtins.toJSON. If you want an example on how to do it for buildkite, see https://github.com/serokell/common-infra/blob/master/flake.nix#L69