From owner-freebsd-current@FreeBSD.ORG Mon Jun 20 19:12:45 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA07116A41C; Mon, 20 Jun 2005 19:12:45 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-66.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACE8A43D48; Mon, 20 Jun 2005 19:12:45 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j5KJCPd1026741; Mon, 20 Jun 2005 13:12:27 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 20 Jun 2005 13:13:44 -0600 (MDT) Message-Id: <20050620.131344.131702703.imp@bsdimp.com> To: deischen@FreeBSD.org From: "M. Warner Losh" In-Reply-To: References: <20050620.125452.102654445.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: phk@phk.freebsd.dk, rwatson@FreeBSD.org, current@FreeBSD.org Subject: Re: Summary: experiences with NanoBSD, successes and nits on a Soekris 4801 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2005 19:12:46 -0000 In message: Daniel Eischen writes: : On Mon, 20 Jun 2005, M. Warner Losh wrote: : : > In message: : > Daniel Eischen writes: : > : How about NO_FOO[_INSTALL], where NO_FOO = no build and no install, : > : and NO_FOO_INSTALL just prevents the install. In theory, you could : > : build the complete system, then use NO_FOO_INSTALL instead of rm(1). : > : > What's wrong with making sure that NO_FOO will work in the install : > case to not install foo when it is set, even if it was unset in the : > build process? : : If it works or can be made to work, then nothing. Actually, looking at the code, it would cause devd to be built, but not installed without changes. Since NO_GXX is defined in the above scenario. I've started to think about how this might be fixed. It really is a 'don't build this because of toolchain depends' as a 'don't build his because I don't want this feature' intertwinglement. Warner