Re: install/56303: On a fresh installation, /tmp on sparc64 is not sticky

[RVP <rvp%SDF.ORG@localhost>]

The following reply was made to PR install/56303; it has been noted by GNATS.

From: RVP <rvp%SDF.ORG@localhost>
To: Andreas Gustafsson <gson%gson.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost, martin%netbsd.org@localhost, roland.illig%gmx.de@localhost,
        Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>, vezhlys%gmail.com@localhost,
        christos%NetBSD.org@localhost
Subject: Re: install/56303: On a fresh installation, /tmp on sparc64 is not
 sticky
Date: Thu, 26 Aug 2021 22:38:37 +0000 (UTC)

 On Thu, 26 Aug 2021, Andreas Gustafsson wrote:
 
 > Yes, _if_ the progress bar has been turned off at that point, but that
 > is not currently the case.  It would be the case if we also applied
 > one of your other changes, moving the progressmeter(1) call to before
 > the wait() calls, but I don't think that change is a good idea; it
 > would cause the progress command to indicate that the operation is
 > complete before the "cmd" has actually finished, and the final
 > transfer rate estimate would no longer account for the full execution
 > time of the "cmd".
 >
 
 Should be OK, seeing as the only metrics used for the progress-bar are
 `filesize' (even if -1) and `bytes'. Ie. progress(1) mainly deals in the
 data it passes through, and not total execution time.
 
 -RVP