| 29 Jun 2025 |
 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 |
