From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 19 Dec 2013 14:09:28 -0500 To: 9fans@9fans.net Message-ID: <0d962f373ebb1452e3504be85d26b7dd@coraid.com> In-Reply-To: References: <3e1e9e6fbfa856a01013a2f51b8d244f@coraid.com> <34270f8ddb3fc06e71d4db496a891dd4@brasstown.quanstro.net> 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: a232c41c-ead8-11e9-9d60-3106f5b1d025 > What I am beginning to understand from comments like this is that there is > a "club Plan-9". Everything ever done by the originators of "club Plan-9" > is correct, period. No mater what exceptions, special cases, or good new > ideas occur, they are wrong and we will find some way of rationalizing > "club Plan-9". Anyone can join "club Plan-9" if you buy into that > assumption. The main purpose of Plan-9 forks (with some exceptions) is to > port to new hardware. Messing with the premise of "club Plan-9" is > significantly frowned upon and attacked. > > Just a newbie's (with 35 years experience) perception. first things first. breaking mk is not a good idea. to see that things could break with < rather than <= one only needs to consider a dependency that might be modified more than once during a build. for example fu.h that is modified for a debug version built along a non-debug version. perhaps there is some truth to this. certainly plan 9 is not perfect. and certainly there are things you will improve. but on the other hand, many of us have quite a bit of experience, too. - erik