[Nix-dev] libpurple and PURPLE_PLUGIN_PATH

Vladimír Čunát vcunat at gmail.com
Fri Jun 9 08:45:38 CEST 2017


On 06/09/2017 02:17 AM, Bryan Richter wrote:
> I see that nixpkgs patches libpurple (pidgin) to look for plugins
> in paths specified by PURPLE_PLUGIN_PATH. Do I have to set that var
> manually?
> 
> I would hope that installing a plugin into my environment would update
> the variable automatically.

You want pidgin.override { plugins = [ ..... ]; }

> Are there other cases in the nixpkgs universe that match this pattern? [...]

Yes, plugin-style packaging is more complicated with nix.  Normally
packages assume there's one directory which collects all plugins of a
particular type, but we typically don't want that, so other ways are used.

--Vladimir

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://mailman.science.uu.nl/pipermail/nix-dev/attachments/20170609/ee28b443/attachment.sig>


More information about the nix-dev mailing list