Controlling Firefox Component Rebuilds During World Update

[DontPanic]

I'm in the process of performing the world update for my Sabayon-Linux x86 3.3b mini version installation, and I'm worried I'm introducing conflicts by trying to stay with the mozilla-firefox-bin packages. Eventually, I'll replace the bin packages with compiled packages, but I'd like to get my USE flags settled out and my world rebuilt first to avoid repetitious rebuilding of the firefox packages.

However, my emerge update keeps pulling in the Netscape nss and nspr packages.

There are already nss and nspr files installed with my mozilla-firefox-bin package. Won't these conflict with each other?

Here's a sample output of what emerge is trying to do:

Code: Select all

 # USE="-firefox" emerge --update --deep --newuse -p world | less -M
Calculating world dependencies  ..... ..... ..... ..... ..... ..... .... done!
[ebuild  N    ] dev-libs/nspr-4.6.5-r1  USE="ipv6 -debug"
  ...
[ebuild  N    ] dev-libs/nss-3.11.5 
  ...
[ebuild     U ] www-client/mozilla-firefox-bin-2.0.0.4 [2.0.0.2] USE="-restrict-
javascript%" LINGUAS="-ro%"
[ebuild     U ] net-www/netscape-flash-9.0.48.0 [9.0.31.0]
  ...
[ebuild     U ] mail-client/mozilla-thunderbird-bin-2.0.0.4 [1.5.0.9] LINGUAS="-
be% -nn% -nn_NO% -pa% -pt% -pt_PT% -zh% -zh_TW%"


[DontPanic]

To follow-up on this thread, I went ahead and let portage build and install the nspr and nss packages.

It doesn't appear to have clobbered anything, and my mozilla-firefox-bin seems to be working fine.