| 15 Mar 2024 |
ryantm | infinisil: I just though it'd be nice to run nix run .#nixpkgs-manual-mmdoc-watch probably not required. | 23:16:55 |
infinisil | ryantm: I feel like exposing a separate attribute in flake.nix would be better | 23:18:30 |
infinisil | ryantm: Like, define it in doc/default.nix primarily, but then do nixpkgsManual = import ./doc or so in flake.nix | 23:19:04 |
infinisil | (also camelCase is the convention in Nixpkgs, not snake_case) | 23:19:52 |
infinisil | But I also get the argument for wanting the same interface between flakes and non-flakes, which wouldn't work with this.. | 23:21:55 |
infinisil | * But I also get the argument o wanting the same interface between flakes and non-flakes, which wouldn't work with this.. | 23:22:01 |
infinisil | * But I also get the argument of wanting the same interface between flakes and non-flakes, which wouldn't work with this.. | 23:22:04 |
infinisil | Nixpkgs is due for a refactoring and API change to make sure we have a single entry-point that exposes everything.. | 23:22:58 |
| 16 Mar 2024 |
| @grahamc:nixos.org joined the room. | 00:04:38 |
| willbush joined the room. | 00:21:10 |
infinisil | willbush: context for others Me and Philip Taron (UTC-8) (who's been reviewing a lot of my nixpkgs-check-by-name PRs) were planning to do a brainstorming session on improving the error collection in the tool, main goal to make NixpkgsProblem not be such a mess.
We haven't scheduled anything yet, would you be interested in joining too? :D
| 03:38:17 |
infinisil | * willbush: (context for others) Me and Philip Taron (UTC-8) (who's been reviewing a lot of my nixpkgs-check-by-name PRs) were planning to do a brainstorming session on improving the error collection in the tool, main goal to make NixpkgsProblem not be such a mess.
We haven't scheduled anything yet, would you be interested in joining too? :D
| 03:38:27 |
willbush | Sure! | 04:09:20 |
infinisil | willbush: Oh can you join my first office hour on Monday perhaps? I believe Philip Taron (UTC-8) is also planning to join: https://discourse.nixos.org/t/community-calendar/18589/120 | 04:13:02 |
| @imincik:matrix.org joined the room. | 08:41:50 |
| mj joined the room. | 14:00:48 |
willbush | In reply to @infinisil:matrix.org willbush: Oh can you join my first office hour on Monday perhaps? I believe Philip Taron (UTC-8) is also planning to join: https://discourse.nixos.org/t/community-calendar/18589/120 I can make it to that | 17:53:23 |
Philip Taron (UTC-8) | I’ll be there too. See you all then! | 18:14:15 |
infinisil | Awesome! | 18:35:00 |
| 17 Mar 2024 |
davidak | i created an issue about package project status, like unmaintained or abandoned. it would be great if you can have a look at some point https://github.com/NixOS/nixpkgs/issues/296646 | 13:12:59 |
hexa | we are piling on metadata and I'm not exactly sure where to draw the line | 13:36:13 |
hexa | if something was unmaintained we could as well remove all maintainers | 13:37:09 |
hexa | if it was abandoned (upstream?) we could should remove it, but there's usually reverse dependencies involved | 13:37:42 |
davidak | one project says: "looking for new maintainer" | 13:38:22 |
davidak | that might take weeks or years | 13:38:35 |
@patka_123:matrix.org | Keeping all this metadata updated manually seems like a recipe for disaster and mistakes imo | 13:42:20 |
infinisil | It would be great if Nixpkgs had more "postprocessing" steps | 13:43:55 |
infinisil | Just like programs.sqlite for binary lookup, we could do the same for maintainer status of packages by automatically checking the date of the source and exposing that in some way | 13:44:35 |
infinisil | How programs.sqlite is distributed is a bit hacky (embedded into the Nixpkgs channel source), but I can imagine better ways | 13:46:09 |
Robert Hensing (roberth) | In reply to @infinisil:matrix.org It would be great if Nixpkgs had more "postprocessing" steps The lack of postprocessing is also a feature. It makes it easy to maintain or use a fork of Nixpkgs | 13:47:43 |