Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-java
Navigation:
Lists: gentoo-java: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Petteri Räty <betelgeuse@g.o>
Subject: Re: [gentoo-dev] browserplugin vs. nsplugin
Date: Mon, 17 Oct 2005 23:41:14 +0300
Aron Griffis wrote:
> Back in July the Java team proposed fixing its ebuilds to respect the 
> USE=browserplugin instead of USE=mozilla, a worthwhile change.  During 
> the course of the discussion, it became clear that the existing 
> USE=nsplugin was more appropriate.
> 
> http://www.mail-archive.com/gentoo-dev@g.o/msg02898.html
> 
> Unfortunately the discussion stagnated and the Java team went ahead 
> with their original suggestion.
> 
> At this point I think it would still be worthwhile to repair these 
> ebuilds to respect USE=nsplugin and drop the browserplugin from 
> use.local.desc.  Comments?

Well I have no problem with changing it again, but our user base might
get a little tired. At least we should put a lot of information out
about the change before going forward with it. We currently still have
the mozilla use flags in the ebuilds and I would not like to see three
different use flags for browser plugins in the ebuilds. Something like a
USE flag move would be a nice feature for portage (to update
/etc/portage/package.use).

Regards,
Petteri Räty (Betelgeuse)

Attachment:
signature.asc (OpenPGP digital signature)
Navigation:
Lists: gentoo-java: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [gentoo-dev] Tomcat 5.5 in portage
Next by thread:
Re: [gentoo-dev] browserplugin vs. nsplugin
Previous by date:
Re: [gentoo-dev] Tomcat 5.5 in portage
Next by date:
Re: [gentoo-dev] browserplugin vs. nsplugin


Updated Jun 17, 2009

Summary: Archive of the gentoo-java mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.