public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Olivier Crête" <tester@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Optional Package Dependencies for netscape-flash	-> libflashsupport
Date: Fri, 11 May 2007 16:06:50 -0400	[thread overview]
Message-ID: <1178914010.8007.26.camel@localhost> (raw)
In-Reply-To: <20070511135253.19192cf2@sed-192.sedsystems.ca>

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

On Fri, 2007-11-05 at 13:52 -0600, Jim Ramsay wrote:
> Thomas Rösner wrote:
> > Jim Ramsay wrote:
> > > [snip]
> > > Have netscape-flash with IUSE="vanilla" (by default it is off),
> > > which when enabled will not pull in libflashsupport.
> > >   
> > 
> > I don't quite see why this is necessary? Or why you do have this
> > discussion?
> 
> I started this discussion to find out the best way to add
> libflashsupport to netscape-flash for users who want the extra features
> that it offers.
> 
> > > This meets the following goals:
> > >
> > > 1) It makes it easy for "regular" users to get netscape-flash with
> > > any additions required by any global USE flags in exactly one step:
> > >  - emerge netscape-flash
> > >   
> > 
> > So, in netscape-flash:
> > RDEPEND="
> >     ssl? ( foo/libflashsupport )
> >     pulseaudio? ( foo/libflashsupport )
> >     esd? ( foo/libflashsupport )
> >     oss? ( foo/libflashsupport )
> > "
> > and IUSE="ssl pulseaudio esd oss gnutls" in libflashsupport (which, as
> > already said, has it's own ebuild)?
> 
> Yes, I considered this, it is option (2) in the original post in this
> thread. However, I do not believe this is the best solution.  Consider
> the case where:
>  - A user has 'ssl' disabled globally
>  - A user sees that netscape-flash now has 'ssl' support, so he/she
> enables 'ssl' just for the netscape-flash ebuild.
>  - The ebuild would then install libflashsupport, but do so without
> actually adding ssl support, which would be quite frustrating to the
> user, and probably generate unnedded bug traffic.
> 
> It would be much more clear to only use the ssl USE flag when it
> actually affects ssl support.

The solution to this is use-based deps.. The short term workaround is to
use built_with_use.

-- 
Olivier Crête
tester@gentoo.org
Gentoo Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-11 20:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 17:00 [gentoo-dev] Optional Package Dependencies for netscape-flash -> libflashsupport Jim Ramsay
2007-05-10 18:20 ` Patrick McLean
2007-05-10 19:11   ` Olivier Crête
2007-05-11 17:15     ` Jim Ramsay
2007-05-11 18:00       ` Josh Saddler
2007-05-11 18:12         ` Jim Ramsay
2007-05-11 18:27           ` Olivier Crête
2007-05-11 19:19             ` Jim Ramsay
2007-05-11 19:29               ` Olivier Crête
2007-05-11 20:03                 ` Jim Ramsay
2007-05-11 19:36               ` Thomas Rösner
2007-05-11 19:52                 ` Jim Ramsay
2007-05-11 20:06                   ` Olivier Crête [this message]
2007-05-12  9:25                   ` [gentoo-dev] " Steve Long
2007-05-11 20:26 ` Ryan Hill
2007-05-12  0:48   ` Josh Saddler

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=1178914010.8007.26.camel@localhost \
    --to=tester@gentoo.org \
    --cc=gentoo-dev@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