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

[Andreas Gustafsson <gson%gson.org@localhost>]

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

From: Andreas Gustafsson <gson%gson.org@localhost>
To: RVP <rvp%SDF.ORG@localhost>
Cc: Andreas Gustafsson <gson%gson.org@localhost>,
    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: Fri, 27 Aug 2021 09:39:59 +0300

 RVP wrote:
 > 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.
 
 It also displays a transfer rate:
 
      100% |*******************************|   680 KiB  264.59 KiB/s    00:00 ETA
 
 The final transfer rate displayed will be based on the current time as
 of the call to progressmeter(1), and since this call is currently made
 after waiting for the "cmd" to exit, it _will_ reflect the total
 execution time.  I don't think making this display less accurate for
 the sake of eliminating two lines of code would be a good trade-off.
 -- 
 Andreas Gustafsson, gson%gson.org@localhost