!VRULIdgoKmKPzJZzjj:nixos.org

Nix Hackers

930 Members
For people hacking on the Nix package manager itself194 Servers

Load older messages


SenderMessageTime
31 Mar 2025
@roberthensing:matrix.orgRobert Hensing (roberth)with the new packaging we've tried to stick as much to established APIs like plain mkDerivation without added fixed-points on top22:10:07
@trofi:matrix.orgtrofi I had to throw away a bunch of .nix code that added env.NIX_CFLAGS_COMPILE =" -D_GLIBCXX_DEBUG"; to nix package because I have no idea how to do it for nix-2.26. For other package sets in nixpkgs my default action of to stick a patch into local nixpkgs checkout because I have no idea how they work from a set to a set. 22:10:17
@roberthensing:matrix.orgRobert Hensing (roberth)I think the packaging layers we've developed for mkDerivation could be useful outside Nix for other meson-based projects22:10:46
@raitobezarius:matrix.orgraitobezariusas I kind of have joint authority over the Nixpkgs packaging of Lix, I read it but I'm not super convinced personally22:11:27
@raitobezarius:matrix.orgraitobezariusI feel like it violates too the principle of least astonishment for packagers and consumers22:11:37
@raitobezarius:matrix.orgraitobezariusLike it's interesting from a technological PoV22:11:42
@raitobezarius:matrix.orgraitobezariusBut I would not use this for Lix because this is far too out of the Overton window on how do you do packaging in Nixpkgs22:12:00
@roberthensing:matrix.orgRobert Hensing (roberth) .overrideAllMesonPackages is like .overrideAttrs but for all packages at once 22:12:10
@raitobezarius:matrix.orgraitobezariusIf it were up to me, I'd have duplicated the experimental packaging and the normal packaging22:12:14
@raitobezarius:matrix.orgraitobezariusAnd keep both for a while while documenting how to do things in the normal way in the newest way22:12:27
@raitobezarius:matrix.orgraitobezarius
In reply to @roberthensing:matrix.org
.overrideAllMesonPackages is like .overrideAttrs but for all packages at once
I kinda don't understand why this is not just like an .override at the scope level
22:12:57
@raitobezarius:matrix.orgraitobezariusand why does it have to be a overrideAllMesonPackages22:13:08
@roberthensing:matrix.orgRobert Hensing (roberth) .override is for a single callPackage call. This is a package set 22:13:29
@raitobezarius:matrix.orgraitobezarius If the package set gets callPackage while taking the scope as args, you can override the packages inside of the set with a single .override call 22:14:25
@raitobezarius:matrix.orgraitobezariusor am I missing something?22:14:31
@roberthensing:matrix.orgRobert Hensing (roberth)We might have to do something like that if overriding is really that important22:14:37
@trofi:matrix.orgtrofiAh, nice. I'll give it a try.22:14:38
@roberthensing:matrix.orgRobert Hensing (roberth) Maybe nix.overrideAttrs could throw a useful error referring to a monolithic nixVersions.nix_mono package to ease the transition 22:17:07
@roberthensing:matrix.orgRobert Hensing (roberth)as well as docs that refer to it22:17:44
@elvishjerricco:matrix.orgElvishJerriccoI've thought about using it for systemd. Like if udev could go back to being a separate package, that would tremendously ease the dependency graph of nixpkgs. The tradeoffs haven't seemed worth it yet though.22:30:40
@raitobezarius:matrix.orgraitobezariusnikstur would be really angry for sure hahaha22:31:54
@elvishjerricco:matrix.orgElvishJerricco It would be handy if I could like... only patch systemd-boot and not have to rebuild everything else. Would save a minute or two per iteration while bug smashing :P Ultimately not worth very much 22:34:56
@Ericson2314:matrix.orgJohn Ericsonyes that would be fantastic!22:35:52
@Ericson2314:matrix.orgJohn EricsonMeson subprojects are such a killer feature22:35:59
@Ericson2314:matrix.orgJohn EricsonI really want to convince other projects to use them more22:36:07
@Ericson2314:matrix.orgJohn Ericsonin general "let downstream manage the depednencies"22:36:17
@Ericson2314:matrix.orgJohn Ericsondon't just through everything into one package because conways law22:36:26
@Ericson2314:matrix.orgJohn Ericsonseparation of concerns, fine-grained packages, downstream does bootstrap --- por que no los tres!22:36:49
1 Apr 2025
@emilazy:matrix.orgemily John Ericson: btw, I wanted to say thanks for engaging, and sorry for getting frustrated. I don't want to stand in the way of reducing version drift, getting rid of autotools, making Nix more modular and maintainable. just want to make sure that the root causes of 2.18 type situations are addressed by getting properly in tune with the constraints Nixpkgs is under 00:52:23
@emilazy:matrix.orgemily(or in the way of properly-defined interfaces in Nixpkgs, either)00:54:28

Show newer messages


Back to Room ListRoom Version: 6