In my experience, the majority of scripts in nixpkgs either put
dependend packages in buildInputs or interpolate them directly into
scripts; adding a package directly as an env var is rare. Why is this
worth giving up the superior readability and fidelity to actual package
name provided by dashes?
On Fri, Oct 10, 2014 at 10:56:13PM +0200, Luca Bruno wrote:
> Dash in package names are cool, because they map to the real package name.
> However I just found a breaker: bash does not support variables with dash.
> $foo-bar or ${foo-bar} or whatever does not work.
>
> Shall we reconsider the use of dash and prefer the underscore instead for
> package names?
> _______________________________________________
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
