Re: Can we increase the print width/column in daemon backtraces

[Ludovic Courtès]

Hi,

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> diff --git a/nix/libstore/build.cc b/nix/libstore/build.cc
>> index 29266f1dd6..94609e07f5 100644
>> --- a/nix/libstore/build.cc
>> +++ b/nix/libstore/build.cc
>> @@ -2247,6 +2247,7 @@ void DerivationGoal::runChild()
>>          Strings envStrs;
>>          foreach (Environment::const_iterator, i, env)
>>              envStrs.push_back(rewriteHashes(i->first + "=" + i->second, 
>> rewritesToTmp));
>> +    envStrs.push_back("COLUMNS=1024");
>>  
>>          /* If we are running in `build-users' mode, then switch to the
>>             user we allocated above.  Make sure that we drop all root
>
> What about merging this then?

This modifies the environment of every single build process, so no.
Environment contents are set in stone, it’s key to reproducibility.

However, what we can do is add COLUMNS to #:env-vars in
‘package-derivation’ on ‘core-updates’ and/or as the default value of
#:env-vars in ‘gexp->derivation’.

HTH!

Ludo’.