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

per-subsystem subsystemInfo definition/parser? #241

Closed
wmertens opened this issue Aug 10, 2022 · 2 comments
Closed

per-subsystem subsystemInfo definition/parser? #241

wmertens opened this issue Aug 10, 2022 · 2 comments
Labels
architecture enhancement New feature or request

Comments

@wmertens
Copy link
Contributor

It feels weird to let subsystemInfo be handled by translator only, especially since there can be many translators, passing settings to the builder is arbitrary, and I guess the discoverer can't see them?

How about a per-subsystem settings module that defines the flags and optionally transforms them?

Then they could also be made available to the overrides?

@DavHau
Copy link
Member

DavHau commented Aug 13, 2022

How about a per-subsystem settings module

Sounds good. Sounds like a use case for nixos modules.

Then they could also be made available to the overrides?

If we were using nixos modules for our interfaces including for configuring individual packages, there won't be a need of overrides anymore.

@wmertens
Copy link
Contributor Author

Right - I think the modules idea is good, let's discuss in #156

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants