-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Module overriding inside home.nix
(e.g. through imports
and disableModules
)
#2740
Comments
Hi, Home Manager supports the For instance, to disable the The See: |
@berbiche I mean supporting Stand-alone installation cannot make use of the NixOS and nix-darwin feature so far. |
imports
and disableModules
)home.nix
(e.g. through imports
and disableModules
)
Hi again @ShamrockLee, I've looked at our module code once more and the |
But I get this:
after having
in my BTW, the Home Manager is set up as a flake (the way I have documented it in the manual). Not sure if it causes any difference: |
@ShamrockLee You used |
Oops! Sorry for the typo, and thanks a lot for your patience! The problem is now solved. |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
Description
I haven't found a way to override the Home Manager modules for standalone without dilect patching to the home-manager source tree.
If is a modular way to override the modules, just as what
imports = [ "path/to/foo", ... ];
anddisableModules = [
bar/baz, ... ]
do on NixOS, is available in Home Manager, users will be able to get modules from multiple sources, and module testing will be a piece of cake.Without such mechanism, changse such as #2718 will be untestable without switching the source branch.
The text was updated successfully, but these errors were encountered: