-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Comments
Ouch, that's very ugly. Those definitely should not be at top-level. |
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. |
There are still |
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:
|
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. |
Is there a guideline on where to put new options?
I can find categories like
ec2
,gnu
,qtPlugins
andzramSwap
in the option root, on the same level as e.g.hardware
,nix
andlib
.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.
The text was updated successfully, but these errors were encountered: