Hi,
Mathijs Kwik skribis:
> Is there a preferred way? Or does it depend on the situation?
I think the preferred way is now the ‘.override’ function that is
automatically added to derivations called with ‘callPackage’ (which goes
well with the ‘packageOverrides’ option of Nixpkgs, though one can
Configuration options seem to me nicer if it's about turning particular
features on/off. In particular, this seems pretty nice for specifying
global preferences for packages, like enabling pulseaudio support,
bluetooth support, etc.
If you use optional arguments and packageOverrides to set them
Hi all,
When writing packages with optional dependencies and other config
options, I can choose to get these options through an optional
argument to the function, or to use getConfig to fetch them from
nixpkgs.config.
Setting them by either nixpkgs.config or by using packageOverrides to
set the e
