!UUqahLbShAYkkrXmKs:matrix.org

DevOS

37 Members
Seeking help and geeking out together on https://github.com/divnix/devos & https://github.com/divnix/digga10 Servers

Load older messages


SenderMessageTime
24 Sep 2021
@ultranix:matrix.orgultranix i just removed my emacs input/output and kept the emacs user profile in mkFlake and it works as expected 19:04:33
@ultranix:matrix.orgultranix * i'm sure it has to do with mkFlake, maybe because the directory/profile name in home.importables.suites (emacs) is the same name as a flake input/output? 19:04:54
@ultranix:matrix.orgultranixi mean except now i cant use the nix-community/emacs-overlay packages19:05:32
@ultranix:matrix.orgultranixi could keep the names different i suppose19:07:14
@aciceri:nixos.devzrsk ultranix: I just tried to add Emacs as you putting a profile inside the users/ folder and I confirm your problem (and workaround i.e. different names).
However I can't help.
19:35:18
@aciceri:nixos.devzrsk But I take the opportunity to ask how to "disable" a mkFlake's output. My use case is this: I added a NixOS configuration for my aarch64 notebook and when I use nix flake check on my pc (which has crosscompiling enabled) it correctly runs but when I put this command in a Github workflow it tells me that "a 'aarch64-linux' with features {} is required to build..." (since the Github runner is an x86_64 machine).
So how can I tell mkFlake/digga to do not generate checks for a particular platform? Any workaround?
19:40:14
@blaggacao:matrix.orgDavid Arnold (blaggacao) That interface sits really at the nix level I guess. You could just override the checks output. 19:41:32
@blaggacao:matrix.orgDavid Arnold (blaggacao) I don't understand the gist of the "emacs"-issue, though. Can you boil it doen? 19:42:17
@blaggacao:matrix.orgDavid Arnold (blaggacao)* That interface sits really at the `nix` level I guess. You could just override the `checks` output. (With `//`, for example)19:43:02
@blaggacao:matrix.orgDavid Arnold (blaggacao)* I don't understand the gist of the "`emacs`"-issue, though. Can you boil it down?19:43:52
@gtrunsec:matrix.org@gtrunsec:matrix.orgemacs-issue? it seems to be an anti-namespace issue?19:44:37
@blaggacao:matrix.orgDavid Arnold (blaggacao)Yeah, I didn't get it 😁😐19:44:52
@blaggacao:matrix.orgDavid Arnold (blaggacao)

Maybe this helps:

rakeLeaves constructs a nested attribute set according to its crawling rules.

importables is passed as specialArgs, either to nixos or to hm.

19:50:52
@blaggacao:matrix.orgDavid Arnold (blaggacao)At least that might give a better sense where something is breaking.19:51:23
@aciceri:nixos.devzrsk
In reply to @blaggacao:matrix.org
That interface sits really at the nix level I guess. You could just override the checks output. (With //, for example)
But can I override checks in the flake outputs only in a certain case?
19:51:38
@blaggacao:matrix.orgDavid Arnold (blaggacao) You'd have to make your own version of checks. You could assign the mkFlakes output to something and then manipulate it. 19:52:38
@blaggacao:matrix.orgDavid Arnold (blaggacao) let output = mkFlakes ... in ... 19:53:45
@aciceri:nixos.devzrsk I understood what you say but I want to override my checks.aarch64-linux only if the host machine (I mean the machine where I executed nix flake check) has binfmt.emulatedSystems = [ "aarch64-linux" ]; 19:54:10
@aciceri:nixos.devzrskThis way the flake wouldn't be pure I think19:54:38
@blaggacao:matrix.orgDavid Arnold (blaggacao)Ah, yeah.19:54:45
@blaggacao:matrix.orgDavid Arnold (blaggacao) You could just build certain checks by hand. 19:55:16
@aciceri:nixos.devzrskCan I read the "currently running configuration" inside a Flake?19:55:29
@blaggacao:matrix.orgDavid Arnold (blaggacao) nix build .#... 19:55:30
@blaggacao:matrix.orgDavid Arnold (blaggacao)(one by one)19:55:34
@aciceri:nixos.devzrsk
In reply to @blaggacao:matrix.org
nix build .#...
Yes, I could make a script that reads nix flake show and then run a sequence of nix build according to the machine where that command is launched
19:56:44
@aciceri:nixos.devzrskA little bit too hacky maybe19:56:54
@blaggacao:matrix.orgDavid Arnold (blaggacao)It's ok. The problem is in the teaying design, I guess.19:57:13
@blaggacao:matrix.orgDavid Arnold (blaggacao)* It's ok. The problem is in the teasting design, I guess.19:57:42
@blaggacao:matrix.orgDavid Arnold (blaggacao)* It's ok. The problem is in the testing design, I guess.19:57:52
@aciceri:nixos.devzrskMmm, I can't understand what you mean19:58:04

Show newer messages


Back to Room ListRoom Version: 6