prebuild sanity checks

[Benjamin Lutz]

[...]
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050818/af984a03/signature.bin