Re: config(5) break down

[Matt Thomas <matt%3am-software.com@localhost>]

On Mar 4, 2010, at 8:14 AM, Masao Uebayashi wrote:

>> Perhaps a first step would be using config(1) and files.* to generate
>> the module makefiles instead of maintaining them by hand...
> 
> cube@ said he did this part long time ago.  The thing is that only fixing
> these tools don't solve all problems magically.  We have to fix wrong 
> instances
> around the tree.
> 
>>> Broken config(5) files will be named like "<module>.conf", because files.*
>>> namespace is insufficient.  For example pci.kmod can't use files.pci.
>> 
>> Huh? I don't understand.
> 
> Let's see the real examples.  sys/conf/files has this:
> 
>       file    net/zlib.c      (ppp & ppp_deflate) | ipsec | opencrypto | 
> vnd_compression

It would be useful to have an option to config where it could warn about 
module-unsafe definitions like this.