| 23 Sep 2023 |
infinisil | I wrote down a strategy for how pkgs/by-name checks could be made more strict over time without randomly breaking stuff: https://github.com/NixOS/nixpkgs/issues/256788 | 00:14:02 |
infinisil | Well it's generic to any CI check really | 00:14:46 |
infinisil | In reply to @infinisil:matrix.org This should be fairly non-controversial, so I'll go ahead with a Nixpkgs PR for this, indicating the slight deviation from the RFC Only a draft for now: https://github.com/NixOS/nixpkgs/pull/256792 | 00:43:49 |
infinisil | Btw here's the RFC 140 milestone aggregating all of these issues/PRs | 00:52:52 |
| 24 Sep 2023 |
| mib 🥐 joined the room. | 12:23:48 |
| 27 Sep 2023 |
| mib 🥐 changed their display name from mib to mib 🥐. | 05:53:09 |
| PowerUser64 joined the room. | 09:30:05 |
PowerUser64 | After RFC 140 is being used, will packages still have categories of some sort? It seems like it would be a waste to get rid of all the work that has been done to classify 80000+ packages. Personally, I learn about a lot of software just by looking at what other packages are in the categories I use the most. | 09:33:14 |
@piegames:matrix.org | There's a separate RFC for that | 09:33:55 |
PowerUser64 | it's also nice when developing a package to be able to see examples of how similar software was packaged right in the same place | 09:34:00 |
PowerUser64 | Ah good to know | 09:34:08 |
PowerUser64 | What number is it? | 09:34:19 |
PowerUser64 | * After RFC 140 is in full effect, will packages still have categories of some sort? It seems like it would be a waste to get rid of all the work that has been done to classify 80000+ packages. Personally, I learn about a lot of software just by looking at what other packages are in the categories I use the most. | 09:35:51 |
@piegames:matrix.org | 156 I think? | 09:36:31 |
PowerUser64 | hmm that one is "No Direct Nixpkgs Pushes" | 09:37:42 |
PowerUser64 | do you know what it might be called? | 09:39:13 |
Rick (Mindavi) | meta.tags or categories or something | 09:39:46 |
PowerUser64 | I searched for categories and tags but got nothing 😕 | 09:40:40 |
PowerUser64 | ah! 146 | 09:43:03 |
PowerUser64 | https://github.com/NixOS/rfcs/pull/146 | 09:43:04 |
PowerUser64 | somehow searching for categories didn't find this? | 09:43:20 |
infinisil | In reply to @poweruser64:matrix.org After RFC 140 is in full effect, will packages still have categories of some sort? It seems like it would be a waste to get rid of all the work that has been done to classify 80000+ packages. Personally, I learn about a lot of software just by looking at what other packages are in the categories I use the most. We can always get that back from the commit history, though new packages won't have that anymore yeah | 09:44:43 |
infinisil | The benefit of those categories is imo less significant that the benefit of improving the all-packages situation | 09:45:59 |
infinisil | But it's great to have more feedback from people about relying on those categories for the other RFC, as you can see it discusses whethere a categorisation is worth having even :) | 09:46:57 |
PowerUser64 | I'm still a little unsure, what's the real problem with all-packages? It's big, but it seems to not be a problem for the most part? | 09:48:07 |
@piegames:matrix.org | I personally just don't want to care about which categories my packages belong into. If we delegate this to a team or something then I'm fine with it | 09:48:16 |
K900 | It's also hard to keep organized | 09:48:18 |
K900 | And categories are hard to choose "correctly" | 09:48:28 |
K900 | So they're all over the place | 09:48:32 |
@piegames:matrix.org | In reply to @poweruser64:matrix.org I'm still a little unsure, what's the real problem with all-packages? It's big, but it seems to not be a problem for the most part? Infinisil had an entire talk about this on NixCon, recommend that | 09:48:38 |