On Mon, Nov 10, 2014 at 10:18 AM, Francisco Ares <fra...@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
