From owner-freebsd-stable Wed Mar 13 14:21:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from lists.blarg.net (lists.blarg.net [206.124.128.17]) by hub.freebsd.org (Postfix) with ESMTP id B8F7337B416 for ; Wed, 13 Mar 2002 14:21:26 -0800 (PST) Received: from thig.blarg.net (thig.blarg.net [206.124.128.18]) by lists.blarg.net (Postfix) with ESMTP id 69467BD63; Wed, 13 Mar 2002 14:21:26 -0800 (PST) Received: from localhost.localdomain ([206.124.139.115]) by thig.blarg.net (8.9.3/8.9.3) with ESMTP id OAA19355; Wed, 13 Mar 2002 14:21:25 -0800 Received: (from jojo@localhost) by localhost.localdomain (8.11.6/8.11.3) id g2DMOOI14815; Wed, 13 Mar 2002 14:24:24 -0800 (PST) (envelope-from swear@blarg.net) To: "Jeffrey J. Mountin" Cc: stable@FreeBSD.ORG Subject: Re: /etc/make.conf question References: <4.3.2.20020312135845.0369fc20@207.227.119.2> <20020312114158.A92910@blackhelicopters.org> <20020312074349.A91204@blackhelicopters.org> <20020312155618.GA9463@raggedclown.net> <20020312114158.A92910@blackhelicopters.org> <4.3.2.20020312135845.0369fc20@207.227.119.2> <4.3.2.20020313115014.034f9180@207.227.119.2> From: swear@blarg.net (Gary W. Swearingen) Date: 13 Mar 2002 14:24:24 -0800 In-Reply-To: <4.3.2.20020313115014.034f9180@207.227.119.2> Message-ID: Lines: 30 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Jeffrey J. Mountin" writes: > No matter, it's not good to publicly suggest non-standard procedures. Wheewww. Matthew and I can consider ourselfs fortunate that we made no suggestions. > Matthew's > "make update buildworld kernel" is even worse as doing an update without > knowing you are in the middle of a mass commit is one way to break a > build. Another way is to use the "standard procedure". It's still not clear to me how four steps is better than one, at least until I understand how to avoid the mid-commit problem. > Better to pull and wait at least a short time before building to ensure > one has all the commits of a change. The wait won't ensure that, of course. How DOES one ensure that? > Of course most don't know pulling sources again and then trying the > build once more *before* complaining of breakage *should* be the first > thing to do, so there are many false alarms. 8-) If *some* observed a common problem and knew how to *avoid* it, *they'd* write a *PR* on the handbook (or other document). I think that's a *standard procedure*. If someone knows, suggest it here: http://www.freebsd.org/send-pr.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message