On 09/18/2009 07:47 AM, Massimiliano Ziccardi wrote:
Thank you Volker, thank you Walt!It seems that adding the xulrunner flag was the right way to go. However euse -i xulrunner says 'Build native browser integration against xulrunner instead of firefox or seamonkey' So.. do I really need xulrunner? I think seamonkey is enought for me... To answer I tried equery d xulrunner [ Searching for packages depending on xulrunner... ] media-video/vlc-0.9.10 (nsplugin & !seamonkey? <net-libs/xulrunner-1.9.1) (nsplugin&!seamonkey? >=net-libs/xulrunner-1.8) www-client/mozilla-firefox-3.0.14 (xulrunner? =net-libs/xulrunner-1.9.0*)
Many packages can use xulrunner. For example I have at least four packages on my machine that use it: firefox, thunderbird, totem, and yelp, so it saves room and time for me to use xulrunner. It's amazing how fast firefox compiles if you already have xulrunner. So, if you plan to use only seamonkey, and none of the other packages that can use xulrunner, then it won't make any difference to you. Bit if you decide later to install one of those other packages then it will save time and disk space to use xulrunner. To see all packages that can use xulrunner, do 'quse xulrunner'.
