-
Notifications
You must be signed in to change notification settings - Fork 108
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
Extract custom system builds from devosSystem out of lib #170
Comments
The reason |
To be clear I'm not saying change the location of devosSystem. I just want to extract out the |
I think this can be tackled now, I don't plan to play with |
I'm not yet sure how to go about doing this. I think an important question to answer is, should there be a user facing api for adding custom builds? If we decide against that, this would just involve adding a few more files to lib to extract the code. |
I think we should start by splitting, then maybe we could get a clearer picture if we need a user facing API. I also think if #91 is implemented, at least a user facing api within that same file hierarchy would be quite ok, since then a rebase would become cheap, also for nix flake template users, even if code is somewhat mixed together. |
We might include exposure to the |
If you do set the |
Reopening, I realized that the list of modules is available in nixos as a So it might actually be possible to obsolete |
implemented in #266 |
Describe the solution you'd like
There should be some way for users to add and edit their own custom system builds for all hosts like what is currently being done for
isoConfig
and in the futurehmConfig
.Describe alternatives you've considered
Edit lib/devos/devosSystem.nix. But optimally the end user shouldn't have to edit a lib function.
Additional context
I think this could be done as a file that defines an attrset mapping builds to nixosSystem's(or darwinSystems, homeConfigurations, robotnixConfigurations). And all builds will be available under
config.system.builds
as is currently being done.related: #168
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: