| 1 |
On 06.11.22 16:52, Michał Górny wrote: |
| 2 |
> On Sun, 2022-11-06 at 16:08 +0100, Florian Schmaus wrote: |
| 3 |
>> Fair point, and I suspected as much. |
| 4 |
>> |
| 5 |
>> Am I right that this does modify ~portage/.gitconfig (so usually |
| 6 |
>> /var/lib/portage/home/.gitconfig)? If so, I wonder if this could be |
| 7 |
>> avoided, e.g., by setting XDG_CONFIG_HOME to $T/.config. But I guess |
| 8 |
>> that has the potential to break other things. And having some eclass |
| 9 |
>> modifying the home directory of the portage user is not probably |
| 10 |
>> something we could live with. It would just we be nice if the |
| 11 |
>> save.directory setting would be just temporary during the emerge, e.g., |
| 12 |
>> set somewhere under T. |
| 13 |
>> |
| 14 |
> |
| 15 |
> HOME |
| 16 |
> All |
| 17 |
> Ditto |
| 18 |
> The full path to an appropriate temporary directory for use by any |
| 19 |
> programs invoked by the ebuild that may read or modify the home |
| 20 |
> directory. [1] |
| 21 |
|
| 22 |
Nice, I wasn't aware that PMS mandates HOME being set. |
| 23 |
|
| 24 |
- Flow |
Archives