| 29 Jun 2025 |
 emily | and brings some value | 18:51:37 |
 ElvishJerricco | IIRC it was like 30M to make minimal offline installable | 18:51:40 |
| emily | for the graphical ISO I don't think it should be anything we target | 18:51:43 |
| emily | but composed of stuff that could be fixed, IIRC | 18:51:58 |
| ElvishJerricco | I'm wondering if we should cut down the normal installation configuration of graphical stuff so the graphical ISO can be offline installable. Like, instead of growing that ISO, shrink the installed stuff. IMO it's good for the two to be representative of each other in terms of feature set to begin with | 18:52:59 |
| emily | diverging from the recommended application set given by GNOME/Plasma is not something the maintainers of those desktops wants to do | 18:53:32 |
| emily | but some of those applications are clearly not useful on the ISO | 18:53:37 |
| emily | we want to ship KDE PIM and all the default wallpapers, because that is the expected Plasma experience | 18:53:49 |
| emily | but we do not want to pay the large costs it takes to offer those prior to installation | 18:53:57 |
| emily | * diverging from the recommended application set given by GNOME/Plasma is not something the maintainers of those desktops want to do | 18:54:05 |
 Alyssa Ross | We could have a flag to nixos-generate-config to disable stuff not installable offline. | 18:54:21 |
 hexa | KDE PIM came with mariadb iirc | 18:54:21 |
| hexa | * KDE PIM came with mariadb iirc, not a great fit | 18:54:26 |
| emily | this is exacerbated by having two DEs on the ISO: "you'd download that anyway" isn't necessarily true, because you'd only download half of it | 18:54:29 |
| emily | for the minimal ISO these tradeoffs aren't present | 18:54:46 |
| Alyssa Ross | So by default you get everything, but you can opt for an offline install that can easily be expanded into the default install later | 18:54:51 |
| emily | that feels like a moving target, because there's already sort of a luck element to your configuration happening to match stuff that is on the ISO store | 18:55:19 |
| hexa | The primary work would be to keep that logic in sync and I'm not sure that will work | 18:55:22 |
| emily | not actual luck, but you get what I mean | 18:55:26 |
| Alyssa Ross | In reply to @hexa:lossy.network
The primary work would be to keep that logic in sync and I'm not sure that will work Can't we have a test? | 18:55:34 |
| emily | you could configure something slightly differently and it pulls in a random package to verify a config at build time and then it breaks | 18:55:39 |
| hexa | We can, but what are we going to do? Block channel bumps on it? | 18:55:54 |
| emily | not if users changing anything about the config at all is part of the use case | 18:55:57 |
| hexa | That sounds excessive | 18:56:00 |
| emily | like | 18:56:00 |
| emily | you could specify a different filesystem | 18:56:03 |
| ElvishJerricco | it isn't | 18:56:05 |
| emily | and it would break | 18:56:07 |
| emily | well ok bad example | 18:56:24 |
| emily | since the FS has to be on the ISO anyway | 18:56:28 |
