| 22 Oct 2022 |
 mei 🌒& | ooh! | 15:33:09 |
 k0kada (he/him) | We just have to figure out how to separate the doom-data-dir between what is writeable and what it is not | 15:33:38 |
| 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 |
