Subject: Re: Use of opt_ headers
To: Peter Seebach <seebs@plethora.net>
From: Quentin Garnier <cube@cubidou.net>
List: tech-kern
Date: 08/28/2006 13:42:26
--D6g6XXj4Aq26AosE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 28, 2006 at 04:21:53AM -0500, Peter Seebach wrote:
[...]
> What is the compelling reason to write two dozen or more different files,
> rather than having a single "options.h" header that everyone includes?

Because if one changes, you get to recompile everything.  Thanks, but
no.  config(1) takes very good care at not touching a file if it hasn't
changed.

> Are we worried about dependency checking on changing options, or what?  I
> haven't built a kernel in years in which I changed any options without a =
make
> clean; does anyone do that still?  (I'm not saying they don't; I've just =
not
> seen it.)

Well, if you have that many cycles to spare...

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--D6g6XXj4Aq26AosE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iQEVAwUBRPLWotgoQloHrPnoAQKGTQgArNM3G0IDuYvXqAGPtoGhMTmPj5Vtah/J
C07fJ3klVyVTYdoKjLJ5KgM32Hbexo4GzlsVGAZ0a67F9OsBRumdP001H6LbrroE
1tJLld3rg4CO7r0H3jjHrk7+c1V5RdqgTZArC1XdMGTanXURRBZ0OsOxEfBzD8Xw
QDP6AnxbOn6p+Il3ZH24WPvicPSRU1agCrk4iFWsOLXqZ3r884jlY1qZUOEOOp0U
rppbsxqKGo3YEELP2eXz8++T8dUmLtMce8+p/H62rMIjq5btqlTGBfus3TBnd4jj
d6Z2v0H8lPpI2BP6GTRQYeH2/e+ZxWOTkDTD9Oqf62CCWsUXmbyiqg==
=AfH+
-----END PGP SIGNATURE-----

--D6g6XXj4Aq26AosE--