> Date: Thu, 26 Mar 2020 01:26:05 +0100 > From: Kamil Rytarowski <n...@gmx.com> > > Upstream (GCC) is strongly against this change (even under __NetBSD__ > ifdef) as /var/tmp is typically larger than /tmp: > > > I'd strongly recommend against this as-is. > > > > The whole reason we prefer /var/tmp is because it's often dramatically > larger > > than a ram-backed /tmp. > > -- by Jeff Law. > > Do we insist on this patch? Can we remove it from local sources?
We should keep the change. There is no semantic justification for putting build-time temporary files in the directory for temporary files that are meant to persist across reboot. These temporary files _cannot_ be used if interrupted -- let alone by a reboot. Going back to /var/tmp would be ridiculous, and a huge performance hit on systems with tmpfs-backed /tmp, for zero real benefit. Abusing /var/tmp has been stupid for over a decade and I'm glad we finally fixed it. Users who actually run out of /tmp space -- which is something that happens noisily, not silently slowing everything down for no apparent reason, and something that I've never heard of happening on machines that do builds -- can easily either (a) add more, or (b) set TMPDIR explicitly.
