public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Nichols <nichoj@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Eclipse and seamonkey
Date: Wed, 05 Jul 2006 07:06:04 -0500	[thread overview]
Message-ID: <44ABAB2C.2040808@gentoo.org> (raw)
In-Reply-To: <44AB1A0A.4020704@seznam.cz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Caster wrote:
> Hi,
> 
> I've got some wonders about Eclipse ebuild... if I understand correctly,
>  gecko-sdk and mozilla is obsolete and seamonkey or firefox should be
> used, so it was changed from gecko-sdk to seamonkey, but:
> - would it be possible to add firefox support instead of just seamonkey?
> I even think some versions had it, but maybe it's just my imagination.
> Most of other stuff builds against firefox fine, eclipse is now the only
> package I have depending on seamonkey without firefox alternative...
> - why is the useflag reversed, using "no-seamonkey" ? there's already
> global flag "seamonkey"...
> 
> Caster

The last time I checked, eclipse did not like firefox-1.5 at all, and
would fail to compile against it. This was with eclipse 3.1, but perhaps
has been changed with 3.2.

As for why it is no-seamonkey instead of seamonkey, it is because we
want seamonkey on by default, and there isn't a way to archive it
otherwise because seamonkey isn't turned on by default on any profile I
am aware of, and we can't set default use flags on a per package basis.

- - Josh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEq6ss8ATTzZyw6sMRAr5gAJ4jM/F37W4HjD6Xyblk+RU+y538qACeLumX
NwRuXkDIygH/z4biIPS1+Vc=
=a+Gn
-----END PGP SIGNATURE-----
-- 
gentoo-java@gentoo.org mailing list



      reply	other threads:[~2006-07-05 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  1:46 [gentoo-java] Eclipse and seamonkey Caster
2006-07-05 12:06 ` Joshua Nichols [this message]

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=44ABAB2C.2040808@gentoo.org \
    --to=nichoj@gentoo.org \
    --cc=gentoo-java@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