From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 19 Dec 2013 00:40:52 -0500 To: 9fans@9fans.net Message-ID: <34270f8ddb3fc06e71d4db496a891dd4@brasstown.quanstro.net> In-Reply-To: References: <3e1e9e6fbfa856a01013a2f51b8d244f@coraid.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] mk time-check/slice issue Topicbox-Message-UUID: a07d4dcc-ead8-11e9-9d60-3106f5b1d025 > So, I think you are saying, that for pieces in a mkfile that take less than > 1s to build it is possible for them to be build again, unnecessarily, when > mk is run again. This is normal and just the way it is. Is that correct? to be more explicit. if a is built from b and mtime(a) <= mtime(b), then mk could fail to rebuild a when it needs to. for correctness, mk must use <= not <. in some cases, it is possible that this will never converge and adding a sleep 1 to the rule helps things converge. certainly if the point is to save time, then one need not bother. on the other hand, if the point is to make mk precise, that goal can be accomplished with a little effort. - erik