I did a new install for mozilla-firefox with use flag "restrict-javascript" and the noscript-plugin got in as an dependency. But this plugin also inserted mozilla-firefox-bin (and some 32-bit-emul-libs) as dependencies into the queue. My solution for now, as it only happens with a new install: 1. USE="-restrict-javascript" emerge mozilla-firefox 2. emerge -1 noscript Reproducible: Always
Yeah, and as soon as we "fix" it, people installing mozilla-firefox-bin will complain about exactly the opposite issue. CANTFIX.
Actually he has a point. Gentoo is a source distribution and as that www-client/mozilla-firefox should be preferred to www-client/mozilla-firefox-bin
Mozilla team, please be so nice and switch the || dependency accordingly.
um, assign...
(In reply to comment #2) > Actually he has a point. Gentoo is a source distribution and as that > www-client/mozilla-firefox should be preferred to > www-client/mozilla-firefox-bin > Mozilla team, please be so nice and switch the || dependency accordingly. Yeah, sure forcing www-client/mozilla-firefox on -bin users makes a lot more sense - since they'll compile it completely needlessly, which is *exactly* what they wanted to avoid by installing -bin. Sigh.
*** Bug 191365 has been marked as a duplicate of this bug. ***
I guess the best solution in this case is to drop the DEPEND line... Thoughts?
Perhaps something like this? -drop DEPEND and RDEPEND in noscript -with USE="restrict-javascript" noscript as POSTDEPEND in mozilla-firefox and mozilla-firefox-bin -in noscript check for /usr/bin/firefox|/usr/bin/firefox-bin, else die "No installed firefox found"
This is a portage flaw, is it not? The resolver should recognize that the RDEPEND="|| ( >=www-client/mozilla-firefox-bin-1.5.0.7 >=www-client/mozilla-firefox-1.5.0.7 )" is met by *at least one* of the packages already on the build list, in this case non-bin mozilla-firefox. Adding another package to fulfill an already-met dependency is wrong.
(In reply to comment #9) > This is a portage flaw, is it not? Yeah, you don't understand what's this bug about, so... can we drop the dependency and close this to prevent more noise please?
I find this bug very strange. I don't want to have both mozilla-firefox and mozilla-firefox-bin installed on my computer. Surely this bug can be fixed in a better way than adding mozilla-firefox-bin to package.mask?
Preferring one over the other is no solution. But emerging *both* isn't a solution, either. I'm not an ebuild wizard so I don't have a solution, but this needs one. I got quite confused over the sudden appearance of mozilla-firefox-bin on my machine. (equery eventually told me it was noscript who dragged it in.) Options?
How about forking the no-script ebuild into noscript and noscript-bin? Sure the underlying portage bug should be fixed but wouldn't this provide a good solution to this problem?
This is no longer an issue with portage-2.2* which has better blocker resolution logic.