The following Mozilla products are out of date, EOL, and ridden with security bugs. Can we start moving them out of the tree? This means identifying the reverse dependencies that still need it first. net-libs/xulrunner:1.8 =www-client/mozilla-firefox-2* =www-client/mozilla-firefox-bin-2*
This is not acceptable at the moment. We have x86-fbsd which can only use 1.8 at the moment. Once they can stabilize a xulrunner-1.9.x version this could be accomplished. I do not see proper support for x86-fbsd until xulrunner-1.9.2 is released.
The mozilla-firefox-bin can probably be removed however, right? Doesn't mozilla-firefox-bin-3* work?
I can not say about -bin packages. You will need to get with them abou that particular instance.
mozilla-firefox-bin never had keywords on bsd or mips, so that should not hold back right now. There's still the issue of reverse dependencies. I'll start opening bug reports and mark them as blockers of this bug.
VLC has this construct in vlc-1.0.1.ebuild: nsplugin? ( seamonkey? ( =www-client/seamonkey-1* ) !seamonkey? ( >=net-libs/xulrunner-1.8 ) ) For me, on x86 with specific unmasks, this is pulling in the 1.8-series xulrunner.
(In reply to comment #5) > VLC has this construct in vlc-1.0.1.ebuild: > > nsplugin? ( > seamonkey? ( =www-client/seamonkey-1* ) > !seamonkey? ( >=net-libs/xulrunner-1.8 ) > ) This should not be pulling in 1.8. You can try adding =net-libs/xulrunner-1.8* into your /etc/portage/package.mask and then run "emerge -uaDv world" to see which package really pulls in that slot. From the DEPEND you pasted there, VLC should not be it.
Re #6: Thank you. After I added that to package.mask, magically all of my odd blocks disappeared.
gone
