| 22 Oct 2022 |
ckie (they/them) | and i do dread my monthly-ish updates but they're just a few hours of merge conflict suffering max | 15:39:38 |
ckie (they/them) | i think maybe we should ask upstream about their plans | 15:40:10 |
ckie (they/them) | if they're gonna bloat their scope more than the balance changes | 15:40:47 |
ckie (they/them) | * 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 |
k0kada (he/him) | Also, the profile changes make zero sense for us, I would like to disable it if possible | 15:44:58 |
ckie (they/them) | searching for existing issues | 15:47:46 |
| * ckie (they/them) is now reading upstream#1708 | 15:52:21 |
k0kada (he/him) | In reply to @ckie:ckie.dev like our impl of straight.el and whatnot is quite inaccurate but yeah If we really think about it, doom-emacs doesn't make too much sense when you have Nix
You can literally have all the advantages of straight.el without dealing with the complexity of it | 16:00:51 |
k0kada (he/him) | However, rewriting doom-emacs in Nix also doesn't seem like a good idea imo | 16:01:15 |
ckie (they/them) | mm yes, we have a balance to deal with | 16:02:09 |
k0kada (he/him) | In reply to @ckie:ckie.dev thoughts on soft fork of the doom repo? Maybe a hard fork could work, where we drop everything related to straight.el and rebuild using the Emacs withPackages | 16:02:16 |
k0kada (he/him) | But them it is our own lol | 16:02:36 |
ckie (they/them) | yeah | 16:02:39 |
ckie (they/them) | In reply to @ckie:ckie.dev mm yes, we have a balance to deal with need to find a way where we can leech off of the main project for most of the effort | 16:03:01 |
ckie (they/them) | we can draw in the last 20% or whatnot | 16:03:11 |
k0kada (he/him) | In reply to @ckie:ckie.dev need to find a way where we can leech off of the main project for most of the effort Maybe we could convince upstream to have a way to skip straight.el entirely | 16:04:10 |
k0kada (he/him) | Something like "just load the packages from this directory" | 16:04:21 |
k0kada (he/him) | Also convince them to use JSON to declare the packages, we could consume it and drop nix-straight.el entirely | 16:05:13 |
ckie (they/them) | it's more intertwined than that | 16:06:51 |
ckie (they/them) | straight.el also decides the package versions | 16:07:00 |
ckie (they/them) | but they can also be locked from within doom | 16:07:15 |
k0kada (he/him) | In reply to @ckie:ckie.dev it's more intertwined than that Yeah, what I meant was more like if upstream maybe could generate its lock for their versions or something after each update | 16:08:26 |
ckie (they/them) | as in doom sync? | 16:08:53 |
k0kada (he/him) | Yeah | 16:09:02 |
k0kada (he/him) | And publish in the repo in a format that we could consume | 16:09:21 |
ckie (they/them) | "the repo"? doom sync is runtime for imperative uesrs | 16:10:19 |