Subject: Re: Request for comments: let config(1) generate LKMs
To: Hiroyuki Bessho <bsh@NetBSD.org>
From: Quentin Garnier <cube@cubidou.net>
List: tech-toolchain
Date: 09/13/2007 15:11:42
--jDJZvxmnOWiGS9cs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 13, 2007 at 06:55:32PM +0900, Hiroyuki Bessho wrote:
[...]
> I'd like some comments before I start further work on this. =20

It looks strangely familiar to me:

http://mail-index.netbsd.org/tech-kern/2004/02/07/0001.html

Heh, config(1) was still config(8) at the time.

FWIW, I've killed that code off my trees a while ago.  I still think
it's a good idea, but it certainly doesn't deal with all the issues
involved when working with LKMs;  it's only a way to compile said
modules.  My patch dealt with some level of dependency though.  I
believe this is where config(1) has its saying, despite what Martin
thinks:  using all the attributes defined in files.* is a very fine-
grained but already existing tool to deal with module dependencies.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.

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

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

iQEVAwUBRuk3DtgoQloHrPnoAQILcwf/Yu4QFFxilyJKAwaXxdSy2nejMI2Z462K
l4r9qr2Z144YpDopmqtiUdNRO6nxiuE6aoR2EPP9J3Czwqo6B2WkO2pkwK38USxp
UYe8Q2YrFYxnxhO5Pvg3WFnC8MqP1Eh99vVCvwkjPudQdbFgAr73S6fhLXD1rk+R
8NknWPWXkdpoAEP1eIYztokJ7hbEpXV6eS+aEkBHm12ffL8ve+U7lObQ0EAi+3JC
RxyeXOhhB8NC57Sd5+6yiOpeKbNUpvsSKMlArUL3MBIS9wxSbAhEshhHpmZw3jtm
GZmFLYtjp74Ola9Hi+BIlBFxIIDuDwQw+4C5+KD2dCPyRjs44o/CeA==
=vrbN
-----END PGP SIGNATURE-----

--jDJZvxmnOWiGS9cs--