-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
refactor!: move whiskers
to catppuccin/whiskers
#239
Conversation
catppuccin/whiskers
catppuccin/whiskers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've removed all configuration relating to whiskers in the flake.nix
but I think that means this will instantly start breaking if users try to upgrade without changing their input.
(Since catppuccin-toolbox.packages.${pkgs.system}.whiskers
would not longer exist. )
I'm assuming we want to go about this in a way that's nicer to nix users?
cc: @nullishamy @isabelroses @getchoo - would appreciate your inputs :D
You should probably add a |
-packages = forEachSystem (pkgs: lib.filterAttrs (_: v: lib.isDerivation v) (pkgs.callPackage ./nix {}));
+packages = forEachSystem (pkgs: lib.filterAttrs (_: v: lib.isDerivation v) (pkgs.callPackage ./nix { }) // { whiskers = throw "This package has been moved to x `github:catppuccin/whiskers`"; } ); and for the overlay {
catppuccin-whiskers = throw "This package has been moved to x `github:catppuccin/whiskers`";
} this is the best way i could think of without refactoring the flake, as it's pretty brittle with this structure |
catppuccin/whiskers
whiskers
to catppuccin/whiskers
No description provided.