| 3 Aug 2025 |
 emily | so "bencode: sort" should be rejected, but checking and fixing the vintage broken comment is not a blocker | 12:28:00 |
| emily | (I can comment as much if you want, but I've found that contributor a little strange to interact with so if you are already reviewing it probably makes sense for you to handle it) | 12:29:11 |
| 4 Aug 2025 |
 Randy Eckenrode | In reply to @emilazy:matrix.org
nor do build inputs go after postPatch (there is no strict convention for all of this, but if you are going to do this kind of churn, explicitly making things comply less with the guidelines in https://github.com/jtojnar/nixpkgs-hammering/blob/b0817c8269798a830bc42f58a01c7543e7c5268a/explanations/attribute-ordering.md is hard to justify) Is this documented anywhere as the convention to use? I’ve been grouping by phases (so build phase stuff together, etc) …. | 23:24:34 |
| emily | I don't think there's any real consensus, but I think the nixpkgs-hammering ordering is something close to what's most common (i.e. probably many packages violate it in some way or another but if you were going to write down the most consistent set of rules you could based on patterns of relative ordering it would be close to that) | 23:25:41 |
| emily | I think some things are pretty strong consensus (passthru and meta last, pname, version, src, and usually outputs and patches before other stuff) | 23:26:31 |
| emily | and everything in between is a little fuzzy | 23:26:35 |
| 5 Aug 2025 |
|  Axel Karjalainen joined the room. | 17:39:37 |
