-
Notifications
You must be signed in to change notification settings - Fork 53
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
Document modules that need Allow From Derivation #172
Comments
Willing to implement it myself, just let me know. |
documenting what modules contain it would be nice. feel free to PR it to our FAQ regarding excluding them from the global enable option: i can see why this might be a requested feature, but i feel would overcomplicate how we actually implement |
For the option my idea was to have 1 place (2 nixos and home manager) where you use This way you don't need to touch Don't know yet how you would test it so that it is not a best effort option. Would this implementation be overcomplicated? |
All the IFD's at the time of writing # IFD's
programs = {
cava.catppuccin.enable = false;
foot.catppuccin.enable = false;
gh-dash.catppuccin.enable = false;
imv.catppuccin.enable = false;
kitty.catppuccin.enable = false; # IFD is inside HM
lazygit.catppuccin.enable = false;
mpv.catppuccin.enable = false;
swaylock.catppuccin.enable = false;
tofi.catppuccin.enable = false;
zathura.catppuccin.enable = false;
};
services = {
dunst.catppuccin.enable = false;
mako.catppuccin.enable = false;
}; |
From my experience, |
I just wanted to chime in and mention that the kitty IFD shouldn't be required in upstream anymore. We'll have to switch to setting |
Someone is already working on this, see #337. |
This was meant to be closed by #246. Thanks for all the work done here! |
An extra readme segment that specifies which modules require Allow From Derivation
or/and an option to exclude those modules from the global enable option.
The text was updated successfully, but these errors were encountered: