Bugzilla Bug 148390

Hi, the usage of linux_chkconfig_present in the sys-fs/cryptsetup-luks ebuilds
will always fail, because linux-info_pkg_setup is not called first, so
KV_OUT_DIR in linux-info will not have been defined.

Here is a patch to fix it, whilst hopefully still satisfying bug #141182 via
usage of the global "build" USE flag. It also uses the "check_extra_config"
routine for checking and reporting the problem, rather than pointing the user
at a kernel option whose location keeps changing, depending on the kernel
version (it's changed again in kernel 2.6.18).

The sys-fs/cryptsetup ebuilds should be changed similarly.

Created an attachment (id=97550) [edit]
cryptsetup-luks-1.0.3-r2.patch

The problem is, we don't use the 'build' nor the 'livecd' USE-flag during our
GRP-set building.

Then ignore the ewarn, or add a "grp" USE flag ;)

fixed in cvs, try -r3

OK.  This is still incorrect.

Running the linux-info_pkg_setup on a system with an unconfigured kernel will
*always* fail.  This means building GRP, LiveCD, or using the Installer.

Packages that are not kernel modules should *never* fail on an unconfigured
kernel.  We never use the "build" USE flag outside of building a stage1
tarball, so the suggestion to use it was completely incorrect.  Instead, the
build check should be removed, and it should be replaced with proper checking. 
Warnings are fine.  Failures are not.

Basically, you have no need to run linux-info_pkg_setup, at all.  Remove the
USE=build check, run the dm-crypt_check, crypto_check, and cbc_check
unconditionally, and remove linux-info_pkg_setup completely, as it doesn't do
anything this package needs to build.  It will complain about the missing
kernel, but it won't fail.

If nobody has any objections, I can go ahead and add this.  This is pretty much
what we did for the 2006.1/2007.0 releases, so we know it works.

go for it.

Ugh... I think linux-info has changed recently.

OK.  I've gone ahead and made the changes to cryptsetup/cryptsetup-luks, but
some code needs to change in linux-info.  As such, I am leaving this bug open
in an attempt to keep you from getting dupes.  I'll close it once the other bug
is resolved and this bug will magically be "fixed" along with linux-info.

Yay!