emacs: give melpa and melpa-stable own scope #36345
Conversation
Melpa and Melpa Stable interfere with each other. Before this, Melpa unstable will pull in dependencies from MelpaStable (even when Melpa has the dependency). This moves melpa unstable and stable into their own scopes to keep them separate.
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
|
Success on aarch64-linux (full log) Partial log (click to expand)
|
Suppose package I can't offer a deep solution to the problem, but count me as a strong -1 on creating multiple Emacs package scopes. The surface problem here is that the packages in Melpa Stable are ancient garbage. I suggest we can solve that problem by dropping Melpa Stable. I have never found a case where a package in Stable worked, but a package in Melpa did not; however, I have found dozens of cases where a Stable package is broken, but the Melpa version works. In the event that a Melpa package is broken, we can always make an individual package override. |
|
An alternative solution to this would be to move "melpaPackages" after "melpaStablePackages" in the scope. That would just switch it so that "unstable" dependencies are always pulled in (instead of always stable dependencies as it is currently). |
|
Here's a an alternative fix for my use case: This would at least get my config working again- but again we run into the multiple versions of the same package issue. The thing I like about the separate scopes is that it doesn't cross melpa and melpa stable so that if you're "smart" at using it, you wouldn't get any conflicts. Right now you're going to have issues if you ever use an unstable package that depends on another unstable package. |
|
Closing in favor of #36423 |
Melpa and Melpa Stable interfere with each other. Before this, Melpa
unstable will pull in dependencies from MelpaStable (even when Melpa
has the dependency). This moves melpa unstable and stable into their
own scopes to keep them separate.
Shouldn't break anything, but interested in feedback if it does.
/cc @mdorman @ttuegel @oxij
Also fixes nix-community/emacs2nix#43 and part of #11503.