On Wed, Jan 23, 2013 at 7:32 AM, Fabio Erculiani <lx...@gentoo.org> wrote: > I hope this is going to be binary package manager friendly. > In Sabayon for instance, kernel sources are not even installed and at > the same time, /proc/config.gz may not even be available. > There were some corner cases in where pkg_setup failed because this > kernel config check stuff was trying to be "smarter" than the user.
Another issue with this sort of thing is that the kernel in /usr/src/linux might not be the kernel that is running, and the kernel that is running might not be the kernel that is running upon the next boot. I think warnings just make sense, but if we're going to make them fatal then at least print out instructions on how to disable them. I suspect that a large number of users will end up disabling config checks though, in which case this feature will provide a false sense of security. If an upgrade could make a user's system unbootable then we should really be warning them about it BEFORE they merge the package. A news item before the change is committed to portage would be more appropriate. I don't want a fatal error during pkg_setup that isn't fatal for 90% of our users because of all the false alarms to be an excuse for developers to put the blame on the user. That amounts to telling our users that if they don't enable some make.conf option then half of the Gentoo devs will cause their builds to break randomly, and if they do enable it the other half of the Gentoo devs will cause their systems to not boot. Rich
