From owner-freebsd-ports@FreeBSD.ORG Wed Aug 17 23:58:56 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D589816A41F for ; Wed, 17 Aug 2005 23:58:56 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C98A43D46 for ; Wed, 17 Aug 2005 23:58:56 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id ABF0D4EA; Thu, 18 Aug 2005 01:58:54 +0200 (CEST) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41343-05; Thu, 18 Aug 2005 01:58:53 +0200 (CEST) Received: from [10.0.0.23] (mini.intranet [10.0.0.23]) by maxlor.mine.nu (Postfix) with ESMTP id E42952D6; Thu, 18 Aug 2005 01:58:50 +0200 (CEST) Message-ID: <4303CF35.400@datacomm.ch> Date: Thu, 18 Aug 2005 01:58:45 +0200 From: Benjamin Lutz User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <20050817195839.GA22027@odin.ac.hmc.edu> In-Reply-To: <20050817195839.GA22027@odin.ac.hmc.edu> X-Enigmail-Version: 0.92.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1389F4DF9B1F8FF72AC13A5A" X-Virus-Scanned: by amavisd-new at maxlor.mine.nu Cc: ports@freebsd.org Subject: Re: prebuild sanity checks X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 23:58:57 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1389F4DF9B1F8FF72AC13A5A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit [...] > Another option might be a new variable (or variables) that ports that > tend to break spectacularly and unobviously can set like: > > BUILD_DEVS= null zero As a potential user of such a variable, I wonder how I'm supposed to figure out which basic system facilities are required by a given piece of software. I think the right thing to do here would be to have the software react more sensibly to such a problem, ie bail out with an error message. In other words: have the people upstream change their software. Btw: I ran into the same problem 2 or so years ago, when I had accidentally overwritten /dev/null with a normal file; things started failing in very interesting ways for no apparent reason. Cheers Benjamin --------------enig1389F4DF9B1F8FF72AC13A5A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) iD8DBQFDA885gShs4qbRdeQRAusiAJ4m8bmM9L9InBn+rxwFMbpOYNWRowCeL+TG bZqDyMHw8ymax9o4r5uOsv0= =8RJo -----END PGP SIGNATURE----- --------------enig1389F4DF9B1F8FF72AC13A5A--