manually to determine if its outdated
or not. There is no 100% automatic way to do this.
Jeff
--
Jeff Garzik | "The universe is like a safe to which there is a
Building 1024 | combination -- but the combination is locked up
MandrakeSoft | in the safe."-- Pet
Roman Zippel wrote:
Hi,
At http://www.xs4all.nl/~zippel/lc/lkc-0.5.tar.gz you can find the
latest version of the new config system. Besides various small bug
fixes, it includes the following changes:
- Improved mouse interface of qconf
- qconf isn't build if QT isn't available
- if ...
Kai Germaschewski wrote:
On Sun, 22 Sep 2002, Jeff Garzik wrote:
AFAICS, quiet only means the same thing as the traditional make
oldconfig, but suppressing questions where the answers are known. (Which
I think is fine)
yeah, that's fine with me too
I was just referring to the following
Roman Zippel wrote:
On Tue, 8 Oct 2002, Linus Torvalds wrote:
Some things made me go eww (but on the whole details):
- I'd prefer the Config.in name, since this has nothing to do with
building, and everything to do with configuration.
Fine with me.
(jgarzik, I think you're overruled
Roman Zippel wrote:
Hi,
On Wed, 9 Oct 2002, Jeff Garzik wrote:
Well, my basic preference is
* something other than Config.new (the original name in your config system)
* something other than Config.in
I think it is a mistake to name a totally different format the same name
as an older
Brendan J Simon wrote:
Simple and boring but how about Config2.in or Config-2.in ???
no offense intended, but:
ug...
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Linus Torvalds wrote:
So instead: how about just Config for the main per-directory
configuration file, with sub-config's being Config.3c5xx and
Config.rrunner.
I like it. I'm glad Sam mentioned sub-configs such as Config.3c5xx,
that's something that was discussed a while ago [and
Roman Zippel wrote:
Hi,
On Wed, 9 Oct 2002, Jeff Garzik wrote:
Which implies that the equivalent of source drivers/net/Config*
(wildcarding) in Roman's system would be useful. Or maybe source
drivers/net and it knows that when given a directory it should scan for
all Config* files
Sam Ravnborg wrote:
[cc: trimmed]
On Thu, Oct 10, 2002 at 10:18:06AM -0400, Jeff Garzik wrote:
Personally I don't care about Config dependency checking... they are
not modified often enough to affect me, and even if they did, dependency
checking based on changes to Config files can get
Sam Ravnborg wrote:
But there is a good reason why they do it.
Take a look at dirvers/video/Config.in for example.
See the size of the big if's. They span several pages if not the whole file.
Why they do this is simple. Only check for PCI once, and group all
PCI stuff there.
With the syntax
10 matches
Mail list logo
