ivtv fails to build on my machine because I am using kernel 2.6.17. It cribs about VIDEO_CX2341X which is of course only present in >=2.6.18. It is fine to fail but a more user friendly message that I need to emerge 0.7.1 would be better. Either ebuild should check for kernel before linux-mod_pkg_setup and inform the user that he should build 0.7.1 instead OR portage should mask out the version > 0.7.1 if kernel is < 2.6.18. This may not be as straightforward, but is cleaner.
You didn't really read the message, did you? <snip> if ! kernel_is 2 6 18; then die "This only works on 2.6.18 kernels" fi </snip>
*** Bug 156419 has been marked as a duplicate of this bug. ***
Jakub, why do you hate me so much? You didn't bother to read the bug and the ebuild. I said check for kernel version should be before the call to linux-mod_pkg_setup. It is dying in check_extra_config where it is checking for VIDEO_CX2341X. It should die sooner than that if the kernel version is a mismatch. And please don't close this bug because the other option I mentioned should be implemented as a feature. Portage should have automatically picked 0.7.1 version because that's what is appropriate for my kernel. PS: I don't know why it filed two bugs. I hit submit once.
I don't hate you. The ebuild clearly tell you that it's _only_ for 2.6.18; thanks, reread it a couple of time.
why do I have to read the ebuild? The message that the failure showed me was that I was missing VIDEO_CX2341X in my config. I hunted the whole source for this config option and I didn't find it. Why do you say it is invalid bug? It is a bug to tell the users that they are missing a config option when they are actually missing a whole kernel. And all you have to change the ebuild. And what about the portage automagic? why is that not a good feature? If a package is not good on a kernel, it should be masked from emerging.
Already told you a couple of times that this version is for 2.6.18 ONLY. So stop this noise, thanks. There's absolutely no way to depend on a particular kernel version, every kernel revision has a separate clot. NOT a bug, don't reopen this
Closed case.
And I already told you that you telling me doesn't fix a thing. Portage should tell the user. What happens to other people who hit this bug? According to you they should read the ebuild too. What is wrong with swapping the checks in the ebuild, so the clear message that "This is a 2.6.18 package only" goes out, instead of XYZ config option is missing. Do you know how much time I spend finding where VIDEO_CX2341X was defined? It shouldn't have failed in the first place. and then it fails with a wrong message. I am telling you to fix the message and even told you how to fix it, you keep closing it as INVALID. What kind of arrogance is that?
Zzzzzzzzzz.
Stop wasting my time, thanks.
"I said check for kernel version should be before the call to linux-mod_pkg_setup. It is dying in check_extra_config where it is checking for VIDEO_CX2341X. It should die sooner than that if the kernel version is a mismatch." Agreed
Fixed in CVS
Thank you, Steve!
