From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev update
Date: Mon, 10 Nov 2014 10:42:27 -0500 [thread overview]
Message-ID: <CAGfcS_=8DTYCfkdspKj1e3pRz29Zv4Mn1wE3mCpspLvftx8bpQ@mail.gmail.com> (raw)
In-Reply-To: <CAHH9eM7WdL5JtuoBAq6Jde+7FOBD2Xd+A+mef83-R7g2cWwAVA@mail.gmail.com>
On Mon, Nov 10, 2014 at 10:18 AM, Francisco Ares <frares@gmail.com> wrote:
>
> So, if I understood something, I will probably have to check this
> configuration entry every time I build a new kernel from now on, because
> "menuconfig" will probably set this on because of its dependencies, is this
> correct?
>
That depends on how you configure your kernels. If you start from
your last kernel config then the setting won't change. If you create
a new config every time, then it depends on how you're creating it.
Dependencies never cause something to be turned on or off. You have
that a bit backwards conceptually. KDE depends on glibc, which means
you can't install KDE if you don't have glibc present. That doesn't
mean that it is impossible to build a system which contains glibc and
not KDE.
Now, if you were talking about reverse-deps that would be another
matter. The kernel config tools won't let you disable a setting which
is a dependency of another setting, though I believe they generally
don't automatically turn things on either. Dependency-management in
the kernel is fairly primitive in general - it does a somewhat-decent
job of not letting you shoot yourself in the foot, as long as you
don't go manually editing .config files, but it can be a bit of a pain
turning on things that are missing dependencies. It definitely isn't
targeted at the "end user."
--
Rich
next prev parent reply other threads:[~2014-11-10 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 13:21 [gentoo-user] udev update Francisco Ares
2014-11-10 14:20 ` Tanstaafl
2014-11-10 14:37 ` Rich Freeman
2014-11-10 15:18 ` Francisco Ares
2014-11-10 15:42 ` Rich Freeman [this message]
2014-11-10 20:35 ` Francisco Ares
2014-11-10 20:59 ` [gentoo-user] " James
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='CAGfcS_=8DTYCfkdspKj1e3pRz29Zv4Mn1wE3mCpspLvftx8bpQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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