From: Giacomo Catenazzi <cate@debian.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux kernel config converter
Date: Thu, 21 Feb 2002 14:28:24 +0100 [thread overview]
Message-ID: <3C74F5F8.3000201@debian.org> (raw)
In-Reply-To: <fa.gq2s5iv.1s4in@ifi.uio.no>
Roman Zippel wrote:
> Hi,
>
> config: ULTRIX_PARTITION
> define_bool
> default: y
> dep: ((!PARTITION_ADVANCED?) && DECSTATION=y)
> bool
> prompt: Ultrix partition table support
> dep: PARTITION_ADVANCED?
> help:
> Say Y here if you would like to be able to read the hard disk
> partition table format used by DEC (now Compaq) Ultrix machines.
> Otherwise, say N.
>
From old discussion in kbuild list:
1) default: Eric proposed to include defaults in configuration,
but it seems that is a bad things, and defaults should be arch
specific. (I don't remember the discussion, but you can
parse the kbuild list, torque.net time)
2) One of the problem in actual configure are the dependencies.
FOO depend on BAR and BEER.
Wat are the possible value of FOO if BAR=m, BEER=y.
In kernel we have some drivers thet need foo to be n or y,
in other cases: n or m.
The logical operators hide the true dependency table.
(don't expect developers read the docs: the logical operators
seems like C operators, so they use like C, but they forget
the third case (=m) ).
Do you use the python identation mode?
giacomo
next parent reply other threads:[~2002-02-21 13:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.gq2s5iv.1s4in@ifi.uio.no>
2002-02-21 13:28 ` Giacomo Catenazzi [this message]
2002-02-21 14:11 ` linux kernel config converter Roman Zippel
2002-02-21 14:32 ` Giacomo Catenazzi
2002-02-21 15:19 ` Roman Zippel
[not found] <fa.fsgrt4v.1bngh9t@ifi.uio.no>
[not found] ` <fa.hp69onv.i7qtq3@ifi.uio.no>
2002-02-21 14:06 ` Giacomo Catenazzi
2002-02-21 14:26 ` Jeff Garzik
2002-02-21 14:39 ` Giacomo Catenazzi
2002-02-21 15:11 ` Jeff Garzik
2002-02-21 16:00 ` Randy.Dunlap
[not found] ` <fa.lqt3hav.190o1i9@ifi.uio.no>
2002-02-21 14:50 ` Giacomo Catenazzi
2002-02-21 14:56 ` David Lang
2002-02-21 15:05 ` Giacomo Catenazzi
2002-02-21 10:48 Roman Zippel
2002-02-21 11:40 ` Jeff Garzik
2002-02-21 12:21 ` Roman Zippel
2002-02-21 12:32 ` Jeff Garzik
2002-02-21 12:54 ` Erik Andersen
2002-02-21 13:21 ` Jeff Garzik
2002-02-21 14:28 ` David Lang
2002-02-21 14:36 ` Jeff Garzik
2002-02-21 14:40 ` David Lang
2002-02-21 15:05 ` Jeff Garzik
2002-02-21 15:41 ` Jason Lunz
2002-02-21 15:54 ` Jeff Garzik
2002-02-21 15:18 ` Alan Cox
2002-02-21 15:08 ` Jeff Garzik
2002-02-21 15:22 ` Gerd Knorr
2002-02-21 15:33 ` Roman Zippel
2002-02-21 18:53 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C74F5F8.3000201@debian.org \
--to=cate@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox