!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

223 Members
https://github.com/nixpkgs-architecture, weekly public meetings on Wednesday 15:00-16:00 UTC at https://meet.jit.si/nixpkgs-architecture49 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
8 Mar 2024
@infinisil:matrix.orginfinisil

Minijackson: This is the most basic thing you could use/copy: https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/by-name-overlay.nix

The sharding doesn't make a lot of sense when you don't have a lot of packages, so I recommend just removing that for personal use

18:23:16
@infinisil:matrix.orginfinisil Really at that point it's just a mapAttrs (name: _: callPackage (./ + "${name}") { }) (readDir ./.) 18:23:56
@infinisil:matrix.orginfinisilFairly standard pattern already :)18:24:08
@Minijackson:matrix.orgMinijacksonthanks a lot!18:24:27
@julienmalka:matrix.org@julienmalka:matrix.org joined the room.18:39:37
@janik0:matrix.org@janik0:matrix.org joined the room.18:55:10
@jakegrin:matrix.orgjakegrin joined the room.19:30:57
@rick.special:matrix.orgrick.special joined the room.19:31:35
@me:indeednotjames.com@me:indeednotjames.com joined the room.19:40:34
@jade_:matrix.org@jade_:matrix.orgI just filed: https://github.com/NixOS/nixpkgs/pull/294353 In writing this I realized that we have both makeExtensible and makeScope. Is there any reason to use makeScope over makeExtensible? Have we written down somewhere secret which one to use in which cases?20:46:54
@jade_:matrix.org@jade_:matrix.orgRelated question: in things like the nix packaging, what is the best practice for exposing internals like the boehmgc-nix package while avoiding unnecessarily confusing users with bonus attributes they probably don't care about? https://github.com/nixos/nixpkgs/blob/9080c3655bf8094f99c8c7cb548fd0ee75928260/pkgs/tools/package-management/nix/default.nix#L17-L16220:49:33
@jade_:matrix.org@jade_:matrix.org (specifically, I want to do a refactor where you can actually use the Nix common here from outside nixpkgs, which is currently not possible) 20:50:11
@infinisil:matrix.orginfinisil
In reply to @jade_:matrix.org
I just filed: https://github.com/NixOS/nixpkgs/pull/294353

In writing this I realized that we have both makeExtensible and makeScope. Is there any reason to use makeScope over makeExtensible? Have we written down somewhere secret which one to use in which cases?
makeScope allows nested scopes to be created that somewhat compose
20:50:29
@infinisil:matrix.orginfinisil That said, I don't think makeExtensible has any benefit over makeScope 20:50:51
@qyriad:katesiria.orgQyriad there is also makeScopeWithSplicing, I definitely don't think there is documentation on which of the three to use in what cases 20:51:03
@jade_:matrix.org@jade_:matrix.org^^^ this is something we really do need docs on20:51:25
@infinisil:matrix.orginfinisilThe splicing version works with cross compilation20:51:28
@infinisil:matrix.orginfinisilThough it's super unintuitive to use 😅20:51:44
@jade_:matrix.org@jade_:matrix.orgI think I have accidentally written the only public documentation on it in https://jade.fyi/blog/flakes-arent-real/ and I think the wiggles callPackage docs still didn't get picked out? can't recall. Anyway our whole callPackage and fixed points stuff really needs some better exposure and docs.20:52:33
@infinisil:matrix.orginfinisil jade_: Very recent! https://github.com/NixOS/nix.dev/pull/935 20:53:06
@jade_:matrix.org@jade_:matrix.org"how are packages composed together in nixpkgs at a higher level than mkDerivation"20:53:11
@jade_:matrix.org@jade_:matrix.org
In reply to @infinisil:matrix.org
jade_: Very recent! https://github.com/NixOS/nix.dev/pull/935
ah, but there should be reference docs for that!
20:53:21
@infinisil:matrix.orginfinisilYeah that too 😅20:53:38
@infinisil:matrix.orginfinisilI'll take any docs at this point!20:53:43

Show newer messages


Back to Room ListRoom Version: 9