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

Clean up the nixos option tree #9726

Closed
Profpatsch opened this issue Sep 8, 2015 · 5 comments
Closed

Clean up the nixos option tree #9726

Profpatsch opened this issue Sep 8, 2015 · 5 comments
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS

Comments

@Profpatsch
Copy link
Member

Is there a guideline on where to put new options?

I can find categories like ec2, gnu, qtPlugins and zramSwap in the option root, on the same level as e.g. hardware, nix and lib.

Apart from fulltext option search it is hard to find anything in the current structure.
I’m all for flat hierachies, mind you, but designed systematically.

@edolstra
Copy link
Member

edolstra commented Sep 8, 2015

Ouch, that's very ugly. Those definitely should not be at top-level.

@vcunat vcunat added the 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS label Sep 8, 2015
@Profpatsch Profpatsch changed the title Concerning the wild growth of the nixos option tree Clean up the nixos option tree Jul 23, 2016
@Profpatsch
Copy link
Member Author

Profpatsch commented Jul 23, 2016

A strategy for the cleanup is needed. Since renaming options causes a lot of user breakage, a sensible deprecation model is needed first. Therefore this issue depends on #15357.

@Nadrieril
Copy link
Member

There are still zramSwap, gnu, dysnomia and powerManagement that look out of place to me. Do we have a deprecation model by now ?

@stale
Copy link

stale bot commented Jun 5, 2020

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 5, 2020
@Profpatsch
Copy link
Member Author

I’ll close this for now, because I don’t think it’s an extremely important thing to do. Grepping for keywords is much easier in any case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS
Projects
None yet
Development

No branches or pull requests

4 participants