You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To build some Emacs Lisp packages in Nix, Twist requires the user to override the derivations (example). At present, the API does not allow easily sharing overrides between multiple users. Ideally, there should be a community-maintained repository for an overlay, and the user should be able to define his/her own overrides in addition to that.
This is applied to both Emacs configurations and nomake. NoMake is a framework for linting and developing Emacs Lisp packages. If a package contains a dynamic module or depends on another package that requires one, it will require an override.
Some packages also have missing dependencies (which are upstream issues), which can be workaround like this.
Provide workarounds as a separate repository, in a form of overlay.
I am currently working on https://github.com/emacs-twist/overrides to finally resolve this issue. After adding a test suite to the repository, I will close this issue.
To build some Emacs Lisp packages in Nix, Twist requires the user to override the derivations (example). At present, the API does not allow easily sharing overrides between multiple users. Ideally, there should be a community-maintained repository for an overlay, and the user should be able to define his/her own overrides in addition to that.
This is applied to both Emacs configurations and nomake. NoMake is a framework for linting and developing Emacs Lisp packages. If a package contains a dynamic module or depends on another package that requires one, it will require an override.
Some packages also have missing dependencies (which are upstream issues), which can be workaround like this.
Refine the configuration API to allow composition of overrides, if necessary.not needed after Expose pkgs attribute from the scope for use in emacs-twist/overrides #128The text was updated successfully, but these errors were encountered: