public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Weyershäuser" <thedude0001@gmx.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Seamonkey vs Mozilla cage match round two
Date: Sat, 18 Nov 2006 08:45:21 +0100	[thread overview]
Message-ID: <455EBA11.3080108@gmx.de> (raw)
In-Reply-To: <20061118072026.GA12976@crowfix.com>

[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]

felix@crowfix.com wrote:
> Something else about this seamonkey vs mozilla conflict has been
> bugging me.  Why are the two even in conflict?  Firefox is not in
> conflict with either one.  Can't they coexist?
> 
Just take a close look at the history of those two packages and their
current status and you should be able to answer that to yourself.

The Mozilla suite is what came out after Netscape decided to opensource
their communicator. At some point Mozilla devs decided that the codebase
was just too complex and rather than fixing it a rewrite would be more
appropriate. That's when Firefox and Thunderbird were born (and one or
more pther projects whose names I don't remember for sure... Sunbird?)

After both Firefox and Thunderbird were somewhat mature the devs decided
that it was time to let go of the Mozilla suite. They announced that
development of it was dead and there would be no more releases, not for
new features, not even for any kind of bugs. Some users of the Mozilla
suite were unhappy about that and started a new project which should
resurrect the Mozilla suite: Seamonkey was born.

Now Firefox was designed to live alongside Mozilla, thereofr the same
goes for Seamonkey. But Seamokey and the Mozilla suite are basically one
and the same program. It was just renamed at some point and then further
developed under the name "Seamonkey". That is why they don't get along
that good.

Another thing you should be aware of: As development (and even
bugfixing) for Mozilla has ceased quite a while ago the last release has
a number of security bugs that are well known and wide open. Any program
using parts of Mozilla are therefor vulnerable as well. For that reason
you shouldn't be using Mozilla and instead switch over to Firefox or
Seamonkey. It will be removed from the tree sooner rather than later.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-11-18  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18  7:20 [gentoo-amd64] Seamonkey vs Mozilla cage match round two felix
2006-11-18  7:45 ` Michael Weyershäuser [this message]
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
2006-11-19  7:26         ` [gentoo-amd64] " Duncan
     [not found] <1163942462.6978.6.camel@ShadowBook.Workgroup>
2006-11-19 13:21 ` [gentoo-amd64] " B Nice

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=455EBA11.3080108@gmx.de \
    --to=thedude0001@gmx.de \
    --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