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

Use hm modules to install extra packages #16

Open
pagusupu opened this issue Jan 26, 2025 · 1 comment
Open

Use hm modules to install extra packages #16

pagusupu opened this issue Jan 26, 2025 · 1 comment

Comments

@pagusupu
Copy link

Would be nice for hm modules to install packages required for plugins, for example right now despite me enabling the starship plugin and having starship enabled through the nixos module, I still need to install the starship package separately.

This will also likely be required for future plugins, like how exifaudio requires the exiftool package and optionally the mediainfo package.

@haennes
Copy link
Contributor

haennes commented Jan 26, 2025

This is a "bug", it´s the exact reason why #9 was merged.
Sadly I currently don´t have time to fix this. But feel free to open a PR.
@lordkekz how should we handle plugins setting home-manager options?
In this case just setting programs.starship.enable would be the way to go.
Should we put setting hm-options behind

  • a global enable / disable
  • a local enable / disable
  • both? (toplevel acting as default)
  • just use mkDefault
  • global + mkDefault

I think that in any of the above cases the assignment should always use lib.mkDefault to grant the user an easy ability to still override

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants