Hi Eelco,
Hmm, I already whipped up a generic solution for long shebangs [1] and
there's the start of a nix build command already. With that already done
it seems likely to be easier to just write a nix shell command rather
than porting nix-shell, why do you think it's preferable to do
otherwise?
Hi Shea,
On 07/29/2016 10:48 PM, Shea Levy wrote:
> For the perl->c++ work, how should we handle nix-shell shebangs given
> that the command is now "nix shell"? Should the nix command itself
> contain shebang-checking logic, or should we have a separate nix-shell
> C++ program just for shebangs,
I've made several PRs and issues, see https://github.com/NixOS/nix/milestone/6
Profpatsch writes:
> On 16-07-29 04:48pm, Shea Levy wrote:
>> Hi Eelco,
>>
>> For the perl->c++ work, how should we handle nix-shell shebangs given
>> that the command is now "nix shell"? Should
On 16-07-29 04:48pm, Shea Levy wrote:
> Hi Eelco,
>
> For the perl->c++ work, how should we handle nix-shell shebangs given
> that the command is now "nix shell"? Should the nix command itself
> contain shebang-checking logic, or should we have a separate nix-shell
> C++ program just for
Hi Eelco,
For the perl->c++ work, how should we handle nix-shell shebangs given
that the command is now "nix shell"? Should the nix command itself
contain shebang-checking logic, or should we have a separate nix-shell
C++ program just for shebangs, or something else?
Thanks,
Shea