Re: [Nix-dev] libpurple and PURPLE_PLUGIN_PATH
On Fri, Jun 09, 2017 at 08:45:38AM +0200, Vladimír Čunát wrote: > 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 = [ . ]; } *lightbulb* Thanks! signature.asc Description: Digital signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] libpurple and PURPLE_PLUGIN_PATH
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 signature.asc Description: OpenPGP digital signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] libpurple and PURPLE_PLUGIN_PATH
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. Are there other cases in the nixpkgs universe that match this pattern? Namely, the use of a library is affected by the availability of plugins, which in turn have build dependencies on the library. Specifying the location of plugins via an environment variable is certainly one solution, but it seems tedious and fragile if there is no way to automatically update the variable on install/upgrade/removal of individual plugins. Perhaps a system of symlinks across store locations would be easy to implement? (Asking as a newcomer to Nix.) Thanks! signature.asc Description: Digital signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev