From: B Nice <Anonymous_Pseudonym_88@yahoo.ca>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Seamonkey vs Mozilla cage match round two
Date: Sun, 19 Nov 2006 13:21:02 +0000 [thread overview]
Message-ID: <BAYC1-PASMTP02B505E2D1B15D5A040963AFEE0@CEZ.ICE> (raw)
Message-ID: <1163942462.6978.6.camel@ShadowBook.Workgroup> (raw)
>I will have to stop using it someday, and I won't bother with an
>overlay. But last time I tried seamonkey it was unstable unreliable
>junk. What I want to understand is why seamonkey and mozilla can't
>coexist. They have different names, but even if they didn't, there
>are slots for apache and apache2, as many different kernels as you
>could possibly want, and ... mozilla and seamonkey conflict with each
>other. Why?
You'll be happy to know that the crashiness of seamonkey had been solved
a couple of months ago. It has been and still is rock solid on my main
system, my better halfs system and <shudder> my gaming system (Read as
Windows XP laptop). I've actually had more trouble with FF collapsing
then with seamonkey. Of course YMMV
As for you main question. Maybe seamonkey and mozilla clash with each
other because they are so close to being the same thing. Some dev
likely looked at it and said that they're too close to bother
differentiating. Hence your current problem, and the problem I faced
when seamonkey was first dropped into the ebuild system with nothing
being built against it.
B Vance
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2006-11-19 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1163942462.6978.6.camel@ShadowBook.Workgroup>
2006-11-19 13:21 ` B Nice [this message]
2006-11-18 7:20 [gentoo-amd64] Seamonkey vs Mozilla cage match round two felix
2006-11-18 7:45 ` Michael Weyershäuser
2006-11-18 14:46 ` felix
2006-11-18 22:35 ` Homer Parker
2006-11-19 0:42 ` felix
2006-11-19 2:34 ` Michael Weyershäuser
2006-11-19 4:12 ` felix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAYC1-PASMTP02B505E2D1B15D5A040963AFEE0@CEZ.ICE \
--to=anonymous_pseudonym_88@yahoo.ca \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox