Portage cannot install firefox from the 2.x and 3.x branches concurrently. Having both versions available is important to web developers and for users who experience bugs during the transition. Running both simultaneously is a separate issue to be filed upstream, as far as I can tell... A workaround is to install www-client/mozilla-firefox-bin for one version and www-client/mozilla-firefox for the other, however this is not always favorable. Reproducible: Always Steps to Reproduce: 1. Install mozilla-firefox-2.x 2. Try to install mozilla-firefox-3.x 3. Portage uninstalls firefox-2 during firefox-3 update Actual Results: Firefox is updated to version 3.x, firefox-2.x is unmerged Expected Results: Firefox-3.x gets installed to a new slot slotted installation will probably require version-specific naming of the firefox binaries and possibly an eselect-based symlink to the default version
Just because you want it, doesn't mean it's (easily) possible. Slotting means in the most of the cases a lot more maintenance overhead Especially since Portage 2.x will likely be not supported for a long while by Mozilla, doing so looks everything else then desirable to me. And if it were, our Mozilla maintainers had done so.
Fair enough. I didn't imagine it would be easy, just that it would make sense. I will explore the possibilities in my local overlay... if anyone else is interested in this let me know. by the way, even if mozilla stops supporting firefox 2.x, I'll still have to.. along with IE6 for some time. It's not like I want IE5/mac and NS4 (;
(In reply to comment #2) > by the way, even if mozilla stops supporting firefox 2.x, I'll still have to.. In your local overlay then, because it will be removed from the repository because of compatibility reasons and very likely vulnerabilities, Mozilla won't fix after a distinct time frame, as with FF 1.5 for example, for sure. btw.: For website testing, the binary FF 2 should really do it and for FF 2 headers you have xulrunner, so I don't see any problem on this side.
