On Wed, Oct 09, 2002 at 10:37:47AM -0700, Linus Torvalds wrote:
> However, I disagree with the naming - I'd rather have one common name for
> the "main" directory entry than have magic rules like "basename of the
> directory capitalized". I don't want to have to search for it.
OK, see your point here.
> I also think I'd perfer to have them all start with the same thing, so
> that (again) it's clear when a directory has multiple configuration files.
>
> So instead: how about just "Config" for the main per-directory
> configuration file, with sub-config's being "Config.3c5xx" and
> "Config.rrunner".
I look at it the other way around. I want to make it clear that there
exist a separate Config file for a given subset of files. The normal
approach is to group files based on their filenames.
Therefore I prefer a fixed suffix, as opposed to a fixed prefix.
ls rrunner*
should show me not only the implementation [.c + .h] but also
the configuration.
The only reason I stick with the .conf prefix for the main per-directory
configuration file is to have a common suffix on all config files.
So I would suggest:
Config.conf <= Main entry in any directory
sensible-name.conf <= Any group of related files
ls *.conf list all configuration files.
ls rrunner* list all files spcific for rrunner
It's so easy to have opinions about naming ;-)
Sam
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
