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

WIP: Displaying package parameters #78

Closed
wants to merge 10 commits into from
Closed

WIP: Displaying package parameters #78

wants to merge 10 commits into from

Conversation

fkz
Copy link

@fkz fkz commented Mar 5, 2016

See also http://thread.gmane.org/gmane.linux.distributions.nixos/19714
Demo: http://schmitthenner.eu/nixos-homepage/nixos/packages.html

Not yet ready for review but I wanted to start collecting a TODO list at a central place.

TODO for being able to publish

  • call the right patched nix version (instead of the hardcoded ~/... path)
  • revert the gunzip (which I need locally because I don't know how pregzipped files work with apache)
  • use allow-unsafe-native-code-during-evaluation instead of patching nix (so we don't have to recompile nix) not possible because we added comment (docstring) parsing to the parser of nix now
  • make displaying stable and unstable versions more general
  • rebase

Other nice additions

  • show default value of optional parameters
  • investigate the "some error happened" packages
  • don't show failed packages (or mark them somehow)
  • show more metadata like comments before parameters (or use more elaborate docstrings etc.)
  • investigate what to do with more elaborate packages, e. g. vim_configurable that uses composableDerivation
  • maybe enable search for parameters
  • make it more beginner friendly: show expression you should insert into .nixpkgs/config.nix

@domenkozar
Copy link
Member

Very nice!

else
[]
else if lib.isList x then
[] # map (mapRecursively "${n}.list") x
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should raise an error, or actually recurse over it.

fkz added 10 commits June 26, 2016 14:17
This uses a heuristic to only include non-package arguments
Also, there seems not to be enough laziness to look into all the derivations; so quite some assertions fail
Furthermore, this needs a forked nixpkgs
namely:
- also allow override in callPackagesWith (which doesn't use makeOverridable)
- support makeOverridable in the functor case
- also build 16.03 channel (not displaying yet)
- better error message when parameters couldn't be determined
… parameter only hides it), 15.09 and 16.03 package sets are both displayed
@samueldr
Copy link
Member

[triage]

Is this still a relevant feature to be developed for the website? The channel selection would be reimplemented in #209, the part about the package parameter isn't, but probably could be ported.

If the feature is desired, but the codebase in need for a rewrite, an issue for the feature request could be opened instead.

@garbas
Copy link
Member

garbas commented Mar 16, 2020

closing this due to inactivity, but if needed please reopen it.

@garbas garbas closed this Mar 16, 2020
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 this pull request may close these issues.

None yet

5 participants