!VRULIdgoKmKPzJZzjj:nixos.org

Nix Hackers

918 Members
For people hacking on the Nix package manager itself192 Servers

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


SenderMessageTime
31 Mar 2025
@joerg:thalheim.ioMic92
In reply to @elvishjerricco:matrix.org
John Ericson: You've got at least 4 nixpkgs maintainers expressing dissatisfaction with the new packaging. It should be clear that something is wrong here. When Mic92 is saying "I could not longer do any work on the code", I think that is demonstrative of the harm I described in my comment. The bare minimum conclusion IMO is that the code is overly complex, and IMO the solution is to delete it and try again.
Not knowing how to update is at least now with the latest pull request from Robert today
20:23:24
@joerg:thalheim.ioMic92* Not knowing how to update is at least now resolved with the latest pull request from Robert today20:23:38
@Ericson2314:matrix.orgJohn Ericson also for the record, I've spend like 15 hours on header stuff that emily requested (and I agreed with) 20:24:38
@Ericson2314:matrix.orgJohn EricsonI am happy that should be wrapping up today20:24:45
@Ericson2314:matrix.orgJohn Ericson nix/util/.....h here we come, not force include config bullshit, and separation of implementation-detail-only vs external-API/-affecting configuration variables woo! 20:25:17
@Ericson2314:matrix.orgJohn Ericson * nix/util/<name>.hh here we come, not force include config bullshit, and separation of implementation-detail-only vs external-API/-affecting configuration variables woo! 20:25:34
@Ericson2314:matrix.orgJohn Ericson * nix/util/<name>.hh here we come, no force-include config bullshit, and separation of implementation-detail-only vs external-API/-affecting configuration variables woo! 20:25:43
@elvishjerricco:matrix.orgElvishJerriccoTo me, I think the ideal solution here is to push all of this back until after 25.05 branchoff. That way 25.05 gets the new Nix version and doesn't require experimental packaging. After branchoff, we can go back to the componentized build and we'll have the length of an entire release cycle to iterate on it and make it ready for 25.1120:28:26
@Ericson2314:matrix.orgJohn Ericson ElvishJerricco: So you are saying do 2.28, but with the monopackage? 20:31:04
@elvishjerricco:matrix.orgElvishJerriccoyea20:31:12
@elvishjerricco:matrix.orgElvishJerricco I don't have any issue with the nix version being bumped for 25.05, though leona expressed some concern about it. My issue is with the packaging expressions making it to the default nix in 25.05 20:32:21
@Ericson2314:matrix.orgJohn Ericson ElvishJerricco: Yeah, not gonna lie 2.28 in Nixpkgs alone is way better than 2.24 20:35:10
@Ericson2314:matrix.orgJohn EricsonI would be fine falling back to that at the first sign of trouble20:35:44
@Ericson2314:matrix.orgJohn Ericsonbut I'm pretty confident the issues are not human not machine? Like while the code needs tto be made legible, but it is working now.20:36:17
@Ericson2314:matrix.orgJohn Ericsonthe touchiest part is the package that combines the other packages20:36:59
@Ericson2314:matrix.orgJohn Ericsonbut as I bump things, I hope to make them not use that20:37:06

Show newer messages


Back to Room ListRoom Version: 6