Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update package config #337

Closed
davidak opened this issue Aug 18, 2021 · 1 comment · Fixed by #405
Closed

Update package config #337

davidak opened this issue Aug 18, 2021 · 1 comment · Fixed by #405

Comments

@davidak
Copy link
Member

davidak commented Aug 18, 2021

@garbas can you update your package config to be in sync with NixOS/nixpkgs#113713, so we have emacsPackages in the search again?

And maybe you can propose a change so the emacsPackages appear as emacs.pkgs as they should after NixOS/nixpkgs#107152. Here is an issue for that: NixOS/nixpkgs#134672

@sternenseemann
Copy link
Member

#405

sternenseemann added a commit to sternenseemann/nixos-search that referenced this issue Dec 31, 2021
The files in nixos-search and nixpkgs have already unnecessarily
diverged — more than they should given that the only difference is that
the search ignores unfree packages (while nixpkgs includes them for the
benefit of repology).

Since we update the NIX_PATH when calling nix-env in nixpkgs_info.rs, we
can simply import the packages-config.nix from nixpkgs using that
information and update it with our addition `allowUnfree = false`.

Resolves NixOS#337.
@garbas garbas linked a pull request Jan 3, 2022 that will close this issue
garbas pushed a commit that referenced this issue Jan 3, 2022
The files in nixos-search and nixpkgs have already unnecessarily
diverged — more than they should given that the only difference is that
the search ignores unfree packages (while nixpkgs includes them for the
benefit of repology).

Since we update the NIX_PATH when calling nix-env in nixpkgs_info.rs, we
can simply import the packages-config.nix from nixpkgs using that
information and update it with our addition `allowUnfree = false`.

Fixes #337.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants