switch mozilla suite -> seamonkey

[Frelon]

Hi,

Everyone knows that mozilla suite is no longer under active development, and the seamonkey project is built on the mozilla "ashes".
So, I tried to emerge seamonkey (with package.unmask and package.keywords tuned, of course), but the problem is that Mozilla blocks :

Code: Select all

newton trunk # ACCEPT_KEYWORDS="~ppc" emerge -p seamonkey

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[blocks B     ] www-client/mozilla (is blocking www-client/seamonkey-1.0)
[ebuild     U ] dev-libs/glib-2.8.6 [2.6.5] 
[ebuild  N    ] x11-libs/cairo-1.0.2  
[ebuild     U ] x11-libs/pango-1.10.4 [1.8.1-r1] 
[ebuild     U ] www-client/mozilla-launcher-1.50 [1.42] 
[ebuild     U ] dev-libs/nspr-4.6.1-r3 [4.4.1-r2] 
[ebuild     U ] dev-libs/nss-3.11-r1 [3.9.2-r3] 
[ebuild     U ] x11-libs/gtk+-2.8.13 [2.6.10-r1] 
[ebuild  N    ] www-client/seamonkey-1.0  

And I don't want to unmerge mozilla !!!

Any idea ???

[freelight]

Seamonkey replaces Mozilla (that's the whole point of Seamonkey). If you want to use it, you will have to unmerge mozilla. Create a binary package of it before you do, just in case. (quickpkg mozilla)

You could, of course, break the dependency tree and run

Code: Select all

emerge --nodeps seamonkey

, but that would most likely break things horribly.

[mark_alec]

Not PPC specific so moved to Portage & Programming.

[Grahammm]

That is not the only problem. It also prevents other packages which use the Mozilla libraries from building as the required header files have moved and the packages are looking in the 'mozilla' location not the 'seamonkey' one.

I did try unmerging mozilla and emerging seamonkey, but the next update wanted to re-merge mozilla as it was a dependency of all the packages with a mozilla USE flag (and some others as well).

So I suspect that the replacement of the Mozilla suite by Seamonkey in the portage tree will not be a simple exercise.

[freelight]

This can probably be fixed by engaging in some dirty hackery. Symlink the expected Mozilla location to the actual Seamonkey location, and add =www-client/mozilla-1.7.12-r2 to /etc/portage/profile/package.provided

To do it properly, the devs would have to create a "mozilla" virtual that could mean Mozilla, Firefox, or Seamonkey. (I think. I'm no dev.)

[aguettinger]

You could try to replace the use flag "mozilla" with "seamonkey" and then do:
emerge --newuse --update --deep world

I'm not sure if that works, though.

[nbargnesi]

Hi,

Everyone knows that mozilla suite is no longer under active development, and the seamonkey project is built on the mozilla "ashes".
So, I tried to emerge seamonkey (with package.unmask and package.keywords tuned, of course), but the problem is that Mozilla blocks :

Code:

newton trunk # ACCEPT_KEYWORDS="~ppc" emerge -p seamonkey

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[blocks B ] www-client/mozilla (is blocking www-client/seamonkey-1.0)
[ebuild U ] dev-libs/glib-2.8.6 [2.6.5]
[ebuild N ] x11-libs/cairo-1.0.2
[ebuild U ] x11-libs/pango-1.10.4 [1.8.1-r1]
[ebuild U ] www-client/mozilla-launcher-1.50 [1.42]
[ebuild U ] dev-libs/nspr-4.6.1-r3 [4.4.1-r2]
[ebuild U ] dev-libs/nss-3.11-r1 [3.9.2-r3]
[ebuild U ] x11-libs/gtk+-2.8.13 [2.6.10-r1]
[ebuild N ] www-client/seamonkey-1.0


And I don't want to unmerge mozilla !!!

Any idea ???

After masking seamonkey, I noticed the dependency requirement was yelp. I peaked at yelp's newest ebuild, and the line

Code: Select all

!sparc? ( !ia64? ( !firefox? ( www-client/seamonkey ) ) )

seems to be what triggers the seamonkey dependency.

A simple adding of firefox to the USE flags fixed this for me, running ~amd64.

[Koala Kid]

Hi,

Everyone knows that mozilla suite is no longer under active development, and the seamonkey project is built on the mozilla "ashes".
So, I tried to emerge seamonkey (with package.unmask and package.keywords tuned, of course), but the problem is that Mozilla blocks :

Code:

newton trunk # ACCEPT_KEYWORDS="~ppc" emerge -p seamonkey

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[blocks B ] www-client/mozilla (is blocking www-client/seamonkey-1.0)
[ebuild U ] dev-libs/glib-2.8.6 [2.6.5]
[ebuild N ] x11-libs/cairo-1.0.2
[ebuild U ] x11-libs/pango-1.10.4 [1.8.1-r1]
[ebuild U ] www-client/mozilla-launcher-1.50 [1.42]
[ebuild U ] dev-libs/nspr-4.6.1-r3 [4.4.1-r2]
[ebuild U ] dev-libs/nss-3.11-r1 [3.9.2-r3]
[ebuild U ] x11-libs/gtk+-2.8.13 [2.6.10-r1]
[ebuild N ] www-client/seamonkey-1.0


And I don't want to unmerge mozilla !!!

Any idea ???

After masking seamonkey, I noticed the dependency requirement was yelp. I peaked at yelp's newest ebuild, and the line

Code: Select all

!sparc? ( !ia64? ( !firefox? ( www-client/seamonkey ) ) )

seems to be what triggers the seamonkey dependency.

A simple adding of firefox to the USE flags fixed this for me, running ~amd64.

It maybe works for those who have firefox compiled from the source. I use firefox-bin, so using your method forces me to have "the other" package

[Koala Kid]

That is not the only problem. It also prevents other packages which use the Mozilla libraries from building as the required header files have moved and the packages are looking in the 'mozilla' location not the 'seamonkey' one.

I did try unmerging mozilla and emerging seamonkey, but the next update wanted to re-merge mozilla as it was a dependency of all the packages with a mozilla USE flag (and some others as well).

So I suspect that the replacement of the Mozilla suite by Seamonkey in the portage tree will not be a simple exercise.

Same here (without "mozilla" USE-flag)

[rm]

amongst others gecko-sharp depends on mozilla for the moment,
not being confident that a simple manual symlink will keep it clean,
I did this:

Code: Select all

  echo "www-client/seamonkey" >> /etc/portage/package.mask
  emerge -C seamonkey
  emerge mozilla

bye,
rm

[hobbes27]

amongst others gecko-sharp depends on mozilla for the moment,
not being confident that a simple manual symlink will keep it clean,
I did this:

Code: Select all

  echo "www-client/seamonkey" >> /etc/portage/package.mask
  emerge -C seamonkey
  emerge mozilla

Code: Select all

emerge -puDv world

These are the packages that would be merged, in order:

Calculating world dependencies /
!!! All ebuilds that could satisfy "www-client/seamonkey" have been masked.
!!! One of the following masked packages is required to complete your request:- www-client/seamonkey-1.0.2 (masked by: package.mask)

For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.
(dependency required by "gnome-extra/yelp-2.14.2-r2" [ebuild])



!!! Problem resolving dependencies for gnome-base/gnome
!!! Depgraph creation failed.

Hm. What do i do now?

[Gergan Penkov]

Mozilla is deprecated and has known security vulnerabilities, this is the relevant gecko-sharp bug http://bugs.gentoo.org/show_bug.cgi?id=98839
the tree should soon be fully moved to seemonkey...

[Kwallo]

Even after removing mozilla with emerge -C and replacing mozilla with seamonkey in make.conf, emerge still complains that mozilla is blocking seamonkey.

[Rafal_Glazar]

Even after removing mozilla with emerge -C and replacing mozilla with seamonkey in make.conf, emerge still complains that mozilla is blocking seamonkey.

This is probably because some package is trying to pull mozilla back. Use -t switch with your emerge command to see which one.

BTW. Is there seamonkey USE flag?

[rm]

yes, there is a seamonkey USE flag, but it's only used by two packages (the moment I checked it out), versus a mozilla USE flag for 50+ ebuilds.

see:
http://gentoo-portage.com/Search?search=&use=seamonkey

bye,
rm

[Loci79]

Why does www-client/mozilla block seamonkey but www-client/mozilla-bin doesn't??

I realized it as I'm running AMD64 with mozilla-bin and now "upgraded" to seamonkey suite.

Is there any hope there'll be a seamonkey-bin ebuild in portage soon?

Loci

[Takesinn]

I think mozilla-bin is installed in /opt/mozilla and not /usr.
But I agree! Why not switch to seamonkey? Is gtk-sharp incompatible with seamonkey? If not then whats the hold up?

[kenjiru]

Replacing mozilla with mozilla-firefox in the ebuild doesn't work. Monodevelop crashes on startup.