Closed cdmistman closed 3 months ago
I know in the wild there are:
I am not sure if the community ever decided on one way. Anyways, this should probably live as a flake part integration in home-manager? And not in the base flake-parts?
i'm not sure if the community ever settled on one, but homeManagerModules
aligns most with the naming conventions elsewhere and is the most explicit.
regardless, i think it's better to have this in flake-parts, so 3rd party flakes don't need to add home-manager as an input when they don't use any other home-manager flake outputs.
Ideally, home manager picks an evalModules
class
name, and then we can add a generic flake.modules.<class>.<module name>
option, to support all the module system applications in one go.
Basically that means to finish
Maybe even add it to the core modules.
Anyways, this should probably live as a flake part integration in home-manager?
That's generally how flake-parts is intended to be extended. Some reasons:
homeManagerModules
aligns most with the naming conventions elsewhere
I'd recommend evalModules { class = "homeManager"; }
to them then. EDIT: Done: https://github.com/nix-community/home-manager/pull/5339
better to have this in flake-parts, so 3rd party flakes don't need to add home-manager as an input when they don't use any other home-manager flake outputs.
That would be a fair reason, but I do think the generic solution (#213) is preferable.
Perhaps unrelatedly, a module that sets homeManagerConfigurations
should definitely live in the home-manager repo, because that's not as simple, and it requires an actual home manager, which is naturally available there.
oooooh i didn't see #213 - that looks like a much better solution :) thank you!
like #223 does for nix-darwin modules, it'd be great to encourage broader sharing of home-manager modules.