This is necessary for seamonkey-2 p.mask removal Reproducible: Always Steps to Reproduce:
Created attachment 215950 [details, diff] gnu-classpath-0.98-r2.ebuild.patch possible patch
(In reply to comment #0) > This is necessary for seamonkey-2 p.mask removal > > Reproducible: Always > > Steps to Reproduce: > We can't fix things to work with seamonkey-2 or?
Unfortunaltely, no. seamonkey-2 doesn't ship any pkg-config files so apps cannot compile against seamonkey-2 anymore.
(In reply to comment #3) > Unfortunaltely, no. seamonkey-2 doesn't ship any pkg-config files so apps > cannot compile against seamonkey-2 anymore. > I am fine with removing it from our packages if seamonkey-1 is going away. If it's going to stay a while we could go with <www-client/seamonkey-2 until it's removed.
(In reply to comment #4) > (In reply to comment #3) > > Unfortunaltely, no. seamonkey-2 doesn't ship any pkg-config files so apps > > cannot compile against seamonkey-2 anymore. > > > > I am fine with removing it from our packages if seamonkey-1 is going away. If > it's going to stay a while we could go with <www-client/seamonkey-2 until it's > removed. > We want to remove it, but at same time without great user end testing it will make it hard to get it out of testing and into stable. Best option is to remove the dep so the move forward can be made just as fast as possible.
This now becomes even more urgent. Upstream officially discontinued seamonkey-1 and also wrote about known unfixed security vulnerabilities. See this news post for reference: http://www.seamonkey-project.org/news#2010-03-16
The nsplugin flag triggering the dep was already masked half year ago and now removed completely.