emacsPackagesNgGen: use import, not callPackage
`callPackage` should only be used for actual packages. Functions, like `emacsPackagesNgGen`, should be `import`ed. This also has the effect of exposing the `override` function provided by `makeScope` so that `emacsPackagesNg.override` overrides the package set instead of overriding the arguments to `emacsPackagesNgGen`.
This commit is contained in:
parent
59f497bc4d
commit
e21f5f933c
@ -11624,10 +11624,11 @@ let
|
||||
|
||||
emacs24Packages = recurseIntoAttrs (emacsPackagesGen emacs24 pkgs.emacs24Packages);
|
||||
|
||||
emacsPackagesNgGen = emacs: callPackage ./emacs-packages.nix {
|
||||
emacsPackagesNgGen = emacs: import ./emacs-packages.nix {
|
||||
overrides = (config.emacsPackageOverrides or (p: {})) pkgs;
|
||||
|
||||
inherit newScope;
|
||||
inherit lib newScope stdenv;
|
||||
inherit fetchFromGitHub fetchgit fetchhg fetchurl;
|
||||
inherit emacs elpaPackages melpaPackages melpaStablePackages;
|
||||
|
||||
trivialBuild = callPackage ../build-support/emacs/trivial.nix {
|
||||
|
Loading…
Reference in New Issue
Block a user