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

Nixpkgs missing its Emacs packages #396

Closed
Atemu opened this issue Jul 30, 2020 · 6 comments
Closed

Nixpkgs missing its Emacs packages #396

Atemu opened this issue Jul 30, 2020 · 6 comments

Comments

@Atemu
Copy link

Atemu commented Jul 30, 2020

Nixpkgs has packaged 254 ELPA and 4601 MELPA packages but none of them show up on repology.org.

They're available under the emacs{25,26}Packages attribute sets (https://search.nixos.org/packages?query=emacs26Packages&from=0&size=10000&sort=relevance&channel=unstable).

@AMDmi3
Copy link
Member

AMDmi3 commented Jul 30, 2020

% wget -qO- https://channels.nixos.org/nixos-unstable/packages.json.br | brotli -d | grep emacs26Packages
%

@Atemu
Copy link
Author

Atemu commented Jul 30, 2020

That's odd.

These definitely are available in Nixpkgs if you evaluate it and the new search page shows them aswell (see link in OP).

I've investigated a bit further and found that nodePackages, perlPackages, luaPackages and texlive packages are also missing.
Some of those do not show up in the new search page either.

I've also looked into how that JSON is generated. It's the result of nix-env -qa which I don't think is a very good source for repository information.
@samueldr @garbas, do we have better sources other than Nixpkgs itself?

Although, would making Repology evaluate Nixpkgs directly be feasible @AMDmi3? That'd be the most accurate source.

@samueldr
Copy link

The issue is that adding a "sub package set" is costly for the packages search interface. Adding new packages into it made the issues with (the older, and the old) package search problematic.

We can look into producing a full list that is independently used for repology import (and other people's data scraping desires).

@AMDmi3
Copy link
Member

AMDmi3 commented Jul 31, 2020

would making Repology Repology evaluate Nixpkgs directly be feasible

Definitely no. I won't do any complex parsing and depend on third party software.

We can look into producing a full list that is independently used for repology import (and other people's data scraping desires).

That would be a solution.

@AMDmi3
Copy link
Member

AMDmi3 commented Aug 27, 2020

Closing since there's nothing to do here on repology side.

@Atemu
Copy link
Author

Atemu commented Dec 24, 2020

Problem has been resolved!

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

No branches or pull requests

3 participants