| 4 Nov 2023 |
|  @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 |
 CRTified | In reply to @mib:kanp.ai
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;
}
Or you use self.lib in the module | 22:03:57 |
| mib 🥐 | In reply to @crtified:crtified.me
Or you use self.lib in the module do you have to pass self down then or is that "automatic"? | 22:04:35 |
| CRTified | What exactly do you mean with "pass down"? If the module is in a separate file, you'll likely have to pass it in some way, but if it's in the same file it is also in the scope, so you don't need to pass it | 22:05:29 |
| mib 🥐 | I'm talking about myModule - same way im passing in lib. | 22:05:49 |
| CRTified | Oh no, not in that way | 22:05:57 |
| CRTified | Give me a sec, I'll try to write a quick example | 22:06:07 |
| CRTified | https://gist.github.com/CRTified/69f83b3c1eef037413a400566e583cd3 | 22:15:11 |
| CRTified | Here you go | 22:15:14 |
| CRTified | Both versions are in that flake 🙂 | 22:16:01 |
| @janik0:matrix.org | In reply to @mib:kanp.ai
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;
}
I think this works, but I also need pass in the nixpkgs lib and the magic nixosModules config attribute somehow | 22:16:05 |
| CRTified | * https://gist.github.com/CRTified/69f83b3c1eef037413a400566e583cd3 Note that the externalModule.nix contains a function taking self which returns the usual module (which is a function in config, lib, ...) | 22:17:35 |
