From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 18 Dec 2013 17:09:41 -0600 Message-ID: From: Jason Catena To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b15a72bd11ad504edd7237e Subject: Re: [9fans] mk time-check/slice issue Topicbox-Message-UUID: a0449158-ead8-11e9-9d60-3106f5b1d025 --047d7b15a72bd11ad504edd7237e Content-Type: text/plain; charset=UTF-8 In part to substitute issues with time with issues with checksums, I am writing a build tool for Inferno loosely inspired by djb's redo. I think it deals nicely with some of the problems of make/mk tools: it handles multiple outputs, treats shell variables as /env files for dependencies, and uses the Inferno shell calling small programs, instead of a domain-specific shell-like language in a build description file. https://github.com/catenate/credo --047d7b15a72bd11ad504edd7237e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In part to substitute issues with time with issues with chec= ksums, I am writing a build tool for Inferno loosely inspired by djb's = redo.=C2=A0 I think it deals nicely with some of the problems of make/mk to= ols: it handles multiple outputs, treats shell variables as /env files for = dependencies, and uses the Inferno shell calling small programs, instead of= a domain-specific shell-like language in a build description file.

https://github= .com/catenate/credo

--047d7b15a72bd11ad504edd7237e--