Concerning a K_DEBLOB_AVAILABLE=0 package such as sys-kernel/git-sources, one can read : << GPL-2 freedist >> which I understand as both AND GPL-2 AND freedist. While concerning any K_DEBLOB_AVAILABLE=1 package such as ck-sources / rt-sources, one can read << GPL-2 !deblob? ( freedist ) >> Which I understand as being GPL-2 AND ( freedist if the deblog use flag is *not* set) If my understanding is correct then I think that things should just be the exact opposite, that is to say : - K_DEBLOB_AVAILABLE=0 packages should *not* display << freedist >> at all, - K_DEBLOB_AVAILABLE=1 packages should display << GPL2 deblob? (freedist) >> Reproducible: Always
No, the logic is correctly. The kernel has blobs in it, covered under the freedist license. K_DEBLOB_AVAILABLE signifies if the deblob tool is supported on this kernel. K_DEBLOB_AVAILABLE=0: The deblob tool DOES NOT support this kernel. LICENSE="GPL-2 freedist" K_DEBLOB_AVAILABLE=1: The deblob tool DOES NOT support this kernel. USE=-deblob -> LICENSE="GPL-2 freedist" USE=deblob -> LICENSE="GPL-2" Ergo: LICENSE="GPL-2 !deblob? ( freedist )"
