[Nix-dev] Reconsidering dash in package names
Anderson Torres
torres.anderson.85 at gmail.com
Sat Oct 11 03:48:02 CEST 2014
I particularly prefer camelCase!
2014-10-10 19:35 GMT-03:00 Shell Turner <cam.turn at gmail.com>:
> Wouldn't it make more sense to simply map foo-bar on a derivation to
> foo_bar as a shell variable? Are there any significant cases where
> this would be problematic?
>
> On 10 October 2014 22:39, Luca Bruno <lethalman88 at gmail.com> wrote:
>> derivation {
>> inherit foo-bar;
>> buildPhase = ''
>> use $foo-bar...
>> '';
>> }
>>
>> Apart ${foo-bar}.
>>
>> On Fri, Oct 10, 2014 at 11:18 PM, Bjørn Forsman <bjorn.forsman at gmail.com>
>> wrote:
>>>
>>> On 10 October 2014 22:56, Luca Bruno <lethalman88 at gmail.com> 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.
>>>
>>> I don't understand. Why/when do we need bash variable _identifiers_
>>> named like packages (with dashes)? And what values would those
>>> "package name variables" contain?
>>>
>>> Best regards,
>>> Bjørn Forsman
>>
>>
>>
>>
>> --
>> www.debian.org - The Universal Operating System
>>
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
More information about the nix-dev
mailing list