| 2 Nov 2023 |
 CRTified | virtu: There is no application attribute, and what you're seeing is the correct output. The systems are generated by flake-utils | 11:04:37 |
| CRTified | * virtu: There is no application attribute, and what you're seeing is the correct (well, more like expected) output. The systems are generated by flake-utils | 11:05:04 |
| CRTified | But nixosModules shouldn't be architecture-specific | 11:05:54 |
| CRTified | Maybe have a look at https://ayats.org/blog/no-flake-utils/#when-things-go-wrong for why you might not need flake-utils (especially if you want to define a nixosModule) | 11:07:01 |
 @virtu:matrix.im | CRTified: yeah, I just realized I had the nixosModules in the wrong place. I figured out a way to fix it in the mean time, but thanks for clarifying and providing some background information. I didn't use flake-utils in my most recent version, but I updated my flake's inputs this morning, switched to out-of-tree poetry2nix because it is no longer in unstable, and started from scratch with a flake template from poetry2nix (which uses flake-utils). I'll do some reading and try to figure out the best approach. thanks! | 11:14:03 |
|  eva changed their profile picture. | 20:09:29 |
|  @adelta:matrix.org joined the room. | 22:43:56 |
| 3 Nov 2023 |
|  @fizihcyst:matrix.org joined the room. | 11:50:24 |
|  mib 🥐 changed their profile picture. | 13:53:21 |
| 4 Nov 2023 |
| @adelta:matrix.org removed their display name Adelta. | 10:32:06 |
| @adelta:matrix.org left the room. | 10:32:08 |
|  @chris01:nitro.chat removed their display name Chris. | 11:53:37 |
| @chris01:nitro.chat left the room. | 11:53:47 |
|  @qyriad:matrix.org joined the room. | 14:42:59 |
| 5 Nov 2023 |
|  @atka:matrix.org joined the room. | 01:15:17 |
|  rjpc joined the room. | 05:12:12 |
| rjpc changed their display name from Ryan Casalino to rjpc. | 05:15:05 |
| rjpc set a profile picture. | 05:15:26 |
| 6 Nov 2023 |
|  Marius changed their profile picture. | 21:26:15 |
| 7 Nov 2023 |
|  loutr joined the room. | 11:29:10 |
 @antifuchs:asf.computer | what are people's thoughts on rime.cx? it seems down, isn't allowlisted in restricted mode by default & ... does http:// URLs only, for a thing that's essentially trust-on-first-use? Is that considered safe? | 13:43:59 |
|  softinio changed their profile picture. | 17:56:18 |
 @janik0:matrix.org | Heyo 👋
I have a flake with two outpus, one is nixosModules and the other one is a lib output. And in the lib output I deine some functions that I would like to use in the nixosModules. The flake looks something like this:
{
description = "A very basic flake";
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
};
outputs = { self, nixpkgs }: {
nixosModules = rec {
myModule = import ./nixos;
default = myModule;
};
lib = ./lib;
};
}
and I'm not quite sure how the wiring for this would work.
I looked at the nixpkgs flake which does lib = lib.extend(some over complicated looking stuff)
Can someone point me in the right direction?
| 20:24:28 |
| @janik0:matrix.org | In reply to @antifuchs:asf.computer
what are people's thoughts on rime.cx? it seems down, isn't allowlisted in restricted mode by default & ... does http:// URLs only, for a thing that's essentially trust-on-first-use? Is that considered safe? I would try to avoid anything relying on a extra piece of infrastructure that is potentially a single point of failure so the whole proxy thing seems quite meh I find the approach https://github.com/snowfallorg/thaw is taking nice so I have to admit I didn't use it yet. | 22:00:09 |
| mib 🥐 | In reply to @janik0:matrix.org
Heyo 👋
I have a flake with two outpus, one is nixosModules and the other one is a lib output. And in the lib output I deine some functions that I would like to use in the nixosModules. The flake looks something like this:
{
description = "A very basic flake";
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
};
outputs = { self, nixpkgs }: {
nixosModules = rec {
myModule = import ./nixos;
default = myModule;
};
lib = ./lib;
};
}
and I'm not quite sure how the wiring for this would work.
I looked at the nixpkgs flake which does lib = lib.extend(some over complicated looking stuff)
Can someone point me in the right direction?
do you actually want to refer to your lib or die you mean to import it first?
if import, then just import it in a let in and pass it to both your modules and lib. something like
outputs = { self, nixpkgs }: {
nixosModules = rec {
default = myModule;
}
}
| 22:02:58 |
| mib 🥐 | In reply to @janik0:matrix.org
Heyo 👋
I have a flake with two outpus, one is nixosModules and the other one is a lib output. And in the lib output I deine some functions that I would like to use in the nixosModules. The flake looks something like this:
{
description = "A very basic flake";
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
};
outputs = { self, nixpkgs }: {
nixosModules = rec {
myModule = import ./nixos;
default = myModule;
};
lib = ./lib;
};
}
and I'm not quite sure how the wiring for this would work.
I looked at the nixpkgs flake which does lib = lib.extend(some over complicated looking stuff)
Can someone point me in the right direction?
* do you actually want to refer to your lib or die you mean to import it first?
if import, then just import it in a let in and pass it to both your modules and lib. something like
(woops one moment hit enter too soon)
outputs = { self, nixpkgs }: {
nixosModules = rec {
default = myModule;
}
}
| 22:03:05 |
| @janik0:matrix.org | In reply to @antifuchs:asf.computer
what are people's thoughts on rime.cx? it seems down, isn't allowlisted in restricted mode by default & ... does http:// URLs only, for a thing that's essentially trust-on-first-use? Is that considered safe? * I would try to avoid anything relying on a extra piece of infrastructure that is potentially a single point of failure so the whole proxy thing seems quite meh I find the approach https://github.com/snowfallorg/thaw is taking nice but I have to admit I didn't use it yet. | 22:03:18 |
| mib 🥐 | * do you actually want to refer to your lib or die you mean to import it first?
if import, then just import it in a let in and pass it to both your modules and lib. something like
(woops one moment hit enter too soon)
outputs = { self, nixpkgs }: let
lib = import ./lib;
in {
nixosModules = rec {
myModule = import ./nixos { inherit lib; };
default = myModule;
};
inherit lib;
}
| 22:03:33 |
| mib 🥐 | * do you actually want to refer to your lib or die you mean to import it first?
if import, then just import it in a let in and pass it to both your modules and lib. something like
outputs = { self, nixpkgs }: let
lib = import ./lib;
in {
nixosModules = rec {
myModule = import ./nixos { inherit lib; };
default = myModule;
};
inherit lib;
}
| 22:03:38 |
| mib 🥐 | * do you actually want to refer to your lib or die you mean to import it first?
if import, then just import it in a let in and pass it to both your modules and lib. something like
outputs = { self, nixpkgs }: let
lib = import ./lib;
in {
nixosModules = rec {
myModule = import ./nixos { inherit lib; };
default = myModule;
};
inherit lib;
}
| 22:03:52 |
