feat: Context for host with home-manager users. #123
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #den > Set user unspecific home-manager options
This changeset introduces a new Den core context:
{ HM-OS-HOST }invoked on host aspects. This context is used by our home-manager integration but can also be used by any other host aspect to detect when HM is enabled, for example to setuseGlobalPkgs.This context is produced by
hm-os-host.nixwhen it detects any host that has an OS supported by home-manager AND has at least one user withhomeManagerclass.The aspect from
hm-os-host.nixis internal, always included inden.default.When
den._.home-managerintegration is enabled, it reacts to thehost-aspect { HM-OS-HOST }context and setups home-manager integration. For each user it callsuser-aspect { HM-OS-USER }for hm-dependencies.nix to include the correct dependencies.home-manager related code has been moved to ./provides/home-manager/.