| 22 Oct 2022 |
 k0kada (he/him) | Because the non-writeable part should be loaded from the straight env | 15:33:51 |
| k0kada (he/him) | (BTW, from what I understand doom-data-dir shouldn't be writeable at all, but upstream doesn't seem to care or is in the process of migration 🤷) | 15:34:27 |
 mei 🌒& | yeah upstream seems quite wonky | 15:34:55 |
| mei 🌒& | i'm definitely on the pessimistic side of this but it feels like we're trying to make a very impure thing pure | 15:35:58 |
| mei 🌒& | thoughts on soft fork of the doom repo? | 15:36:26 |
| k0kada (he/him) | I fear us forking doom repo will mean that we eventually get a really broken system in the future | 15:36:57 |
| k0kada (he/him) | Because the Emacs ecosystem moves fast | 15:37:05 |
| k0kada (he/him) | And doom-emacs has some really low level integration with a few packages | 15:37:16 |
| mei 🌒& | we're currently doing a WINE i think | 15:37:31 |
| mei 🌒& | like our impl of straight.el and whatnot is quite inaccurate but yeah | 15:38:49 |
| mei 🌒& | there's a lot of cogs in the machine | 15:38:54 |
| mei 🌒& | i just wonder because like, i have a private nixpkgs branch: | 15:39:19 |
| mei 🌒& | 
Download image.png | 15:39:23 |
| mei 🌒& | and i do dread my monthly-ish updates but they're just a few hours of merge conflict suffering max | 15:39:38 |
| mei 🌒& | i think maybe we should ask upstream about their plans | 15:40:10 |
| mei 🌒& | if they're gonna bloat their scope more than the balance changes | 15:40:47 |
| mei 🌒& | * if they're gonna bloat their scope more then the balance changes | 15:40:53 |
| k0kada (he/him) | Well, yeah | 15:43:09 |
| k0kada (he/him) | Maybe if we could ask upstream to be more careful | 15:43:19 |
| k0kada (he/him) | What is actually mutable, what it is not | 15:43:34 |
| k0kada (he/him) | Maybe having a separate file too defining those things so we don't need to fix our patches on every change | 15:43:53 |
