Open trofi opened 2 years ago
I also ran ran face-first into this problem with the pidgin-with-plugins
deprecation. Having a separate -unwrapped
attribute makes sense, and fits with other wrapped packages (e.g. firefox).
Incidentally, I also ran into this using the old-style packageOverrides
. For anyone else who runs into this before an fix is merged, a simple workaround is to name your overridden package pidgin-with-plugins while still overriding the pidgin package. in the original example in this issue:
$ nix build --impure --expr 'with import ./. { overlays = [(final: prev: { pidgin-with-plugins = prev.pidgin.override ({ plugins = [prev.pidgin-window-merge]; }); })]; }; pidgin-with-plugins'
Or what I actually have in my .nixpkgs/config.nix:
{
...
packageOverrides = pkgs: rec {
pidgin-with-plugins = pkgs.pidgin.override {
plugins = [ pkgs.pidgin-otr pkgs.pidgin-osd pkgs.purple-hangouts pkgs.purple-googlechat ];
};
}
Describe the bug
I would prefer
pidgin
to always containwindow_merge
plugin. Here is my attempt:Before that I used
pidgin-with-plugins
attribute for the similar purpose.I think recursion is a manifestation of confusion of
pidgin
being an SDK for plugins (and binary itself) andpidgin
being a wrapper around SDK, pidgin binary and plugins. Should plugins use some other attribute?Notify maintainers
@vcunat
One of the options would be to always use wrapper that embeds unwrapped pidgin:
Or alternatively expose 2 attributes:
pidgin
(with meaning of formerpidgin-with-plugins
)pidgin-unwraped
(with meaning of formerpidgin
without plugins)