1 |
2014-11-10 13:42 GMT-02:00 Rich Freeman <rich0@g.o>: |
2 |
|
3 |
> On Mon, Nov 10, 2014 at 10:18 AM, Francisco Ares <frares@×××××.com> wrote: |
4 |
> > |
5 |
> > So, if I understood something, I will probably have to check this |
6 |
> > configuration entry every time I build a new kernel from now on, because |
7 |
> > "menuconfig" will probably set this on because of its dependencies, is |
8 |
> this |
9 |
> > correct? |
10 |
> > |
11 |
> |
12 |
> That depends on how you configure your kernels. If you start from |
13 |
> your last kernel config then the setting won't change. If you create |
14 |
> a new config every time, then it depends on how you're creating it. |
15 |
> |
16 |
> Dependencies never cause something to be turned on or off. You have |
17 |
> that a bit backwards conceptually. KDE depends on glibc, which means |
18 |
> you can't install KDE if you don't have glibc present. That doesn't |
19 |
> mean that it is impossible to build a system which contains glibc and |
20 |
> not KDE. |
21 |
> |
22 |
> Now, if you were talking about reverse-deps that would be another |
23 |
> matter. The kernel config tools won't let you disable a setting which |
24 |
> is a dependency of another setting, though I believe they generally |
25 |
> don't automatically turn things on either. Dependency-management in |
26 |
> the kernel is fairly primitive in general - it does a somewhat-decent |
27 |
> job of not letting you shoot yourself in the foot, as long as you |
28 |
> don't go manually editing .config files, but it can be a bit of a pain |
29 |
> turning on things that are missing dependencies. It definitely isn't |
30 |
> targeted at the "end user." |
31 |
> |
32 |
> -- |
33 |
> Rich |
34 |
> |
35 |
> |
36 |
|
37 |
I guess that last statement includes "genkernel" users. |
38 |
|
39 |
Thanks, |
40 |
Francisco |