Date: Thu, 18 Aug 2005 01:58:45 +0200 From: Benjamin Lutz <benlutz@datacomm.ch> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: ports@freebsd.org Subject: Re: prebuild sanity checks Message-ID: <4303CF35.400@datacomm.ch> In-Reply-To: <20050817195839.GA22027@odin.ac.hmc.edu> References: <20050817195839.GA22027@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4303CF35.400>