21 Jul 2021 |
fufexan | now I'm not sure if callPackage is the way to do this, but it seems to work with neither that nor import ... {} | 20:48:56 |
David Arnold (blaggacao) | Overlays would have to be applyed, then the packages are avaliable as usual. Something like:
{
pkgs = import nixpkgs { config = {}; overlays [ osu."nixpkgs/wine-tkg" osu."nixpkgs/winestreamproxy" ];};
wine-tkg = pkgs.wine-tkg;
}
| 20:55:10 |
David Arnold (blaggacao) | * Overlays would have to be applyed, then the packages are avaliable as usual. Something like:
{
pkgs = import nixpkgs { config = {}; overlays [osu."nixpkgs/wine-tkg" osu."nixpkgs/winestreamproxy" ];};
wine-tkg = pkgs.wine-tkg;
}
| 20:55:16 |
David Arnold (blaggacao) | * Overlays would have to be applyed, then the packages are avaliable as usual. Something like:
{
pkgs = import nixpkgs { config = {}; overlays [
osu."nixpkgs/wine-tkg" osu."nixpkgs/winestreamproxy"
];};
wine-tkg = pkgs.wine-tkg;
}
| 20:55:28 |
fufexan | 😲 that makes sense | 20:55:32 |
fufexan | I haven't thought of that | 20:55:37 |
David Arnold (blaggacao) | Beware, the order of overlays is important. so wine-tkg overlay would have to go before winestreamproxy overlay | 20:56:16 |
David Arnold (blaggacao) | * Overlays would have to be applied, then the packages are avaliable as usual. Something like:
{
pkgs = import nixpkgs { config = {}; overlays [
osu."nixpkgs/wine-tkg" osu."nixpkgs/winestreamproxy"
];};
wine-tkg = pkgs.wine-tkg;
}
| 20:57:10 |
David Arnold (blaggacao) | * Overlays would have to be applied, then the packages are available as usual. Something like:
{
pkgs = import nixpkgs { config = {}; overlays [
osu."nixpkgs/wine-tkg" osu."nixpkgs/winestreamproxy"
];};
wine-tkg = pkgs.wine-tkg;
}
| 20:57:18 |
fufexan | now nix flake check fails with
error: attribute 'currentSystem' missing
at /nix/store/vmcb8svgl9h84mkqmg1nazl9zgpgn7q0-source/pkgs/top-level/impure.nix:18:43:
17| # (build, in GNU Autotools parlance) platform.
18| localSystem ? { system = args.system or builtins.currentSystem; }
| ^
19|
| 21:00:21 |
fufexan | oh wait not this one | 21:00:47 |
fufexan | okay it seems like it was that one | 21:01:34 |
David Arnold (blaggacao) | when using nix flake (pure by default) builtins.currentSystem, as an impurity, is not available. | 21:01:39 |
David Arnold (blaggacao) | * when using nix flake (pure by default) builtins.currentSystem , as an impurity, is not available. | 21:01:46 |
fufexan | then how should I set the system for pkgs ? | 21:02:05 |
David Arnold (blaggacao) | I can't say much about the concrete reasons of the above error, though. | 21:02:14 |
fufexan | I feel like I'm either over-complicating something or overlays are that complicated themselves | 21:02:41 |
fufexan | maybe I shouldn't do what I want using overlays? | 21:02:53 |
David Arnold (blaggacao) | when you use fup you can pass overlays to the channel's overlaysBuilder | 21:03:55 |
David Arnold (blaggacao) | Then fup will spit out self.pkgs.<channelname> with the overlays applied. | 21:04:20 |
fufexan | oh, so that will propagate and I will be able to use prev.wine-tkg for example? | 21:04:53 |
fufexan | I wouldn't want to export those overlays again, but if this makes things easier I don't mind | 21:05:48 |
fufexan | thanks! | 21:05:50 |
David Arnold (blaggacao) | I think self.pkgs is also system scoped so it'd be rather self.pkgs.<system>.<channel> | 21:05:52 |
David Arnold (blaggacao) | (didn't double check right now) | 21:06:02 |
fufexan | sounds right | 21:06:15 |
David Arnold (blaggacao) | you can also use digga 🤣👍️ | 21:06:34 |
David Arnold (blaggacao) | It tries to make that aspect as simple as it can get: https://digga.divnix.com/api-reference-channels.html#channelsnameoverlays | 21:07:07 |
fufexan | I will check it out, thanks | 21:11:03 |
fufexan | oh, I just realized that exportOverlays intelligently figured out those overlays come from an input so it didn't export them again | 21:25:39 |