public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Josh Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Optional Package Dependencies for netscape-flash -> libflashsupport
Date: Fri, 11 May 2007 11:00:31 -0700	[thread overview]
Message-ID: <4644AF3F.7030503@gentoo.org> (raw)
In-Reply-To: <20070511111555.5f26e596@sed-192.sedsystems.ca>

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

Jim Ramsay wrote:
> Olivier Crête wrote:
>> On Thu, 2007-10-05 at 14:20 -0400, Patrick McLean wrote:
>>> Jim Ramsay wrote:
>>>> 1) Create a single local USE flag (flashsupport or something)
>>>> that will just pull in this dependency.
>>>>
>>>> 2) Use the same set of USE flags as libflashsupport has, with any
>>>> of them adding libflashsupport to the dep list, since these are
>>>> all global flags and will most likely be enabled for both
>>>> netscape-flash and libflashsupport
>>>>
>>>> I'm personally thinking (1) is the better of the 2 options, but
>>>> I'd like to know if anyone has any other wondrous solutions to
>>>> this.
>>> Does/will anything else dep on flashsupport? If not, why not just
>>> add the USE flags to netscape-flash and install libflashsupport as
>>> part of the netscape-flash install instead of a separate package.
>> If its a separate package that will be updated separately, then it
>> doesn't make sense to put it in the separate package and I support
>> option 1. Otherwise, if they'll always be together, then just put it
>> in the same package.
> 
> Yes, libflashsupport is distributed separately and is on a different
> release schedule than netscape-flash.
> 
> I suppose I could also propose:
> 
> 4) netscape-flash just RDEPENDS on libflashsupport all the time.  It's
> certainly not a large library to be added on.
> 

That is a terrible idea. Don't make it "depend" on something that it
clearly does *not* depend on. Flash works just fine without the optional
add-ons, and those are *definitely* optional. I've never needed
libflashsupport and would prefer not seeing useless cruft attached to a
perfectly working Flash installation.

If you're going to add it to USE, then make sure it's *not* on by
default, thanks.


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

  reply	other threads:[~2007-05-11 18:05 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 [this message]
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
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=4644AF3F.7030503@gentoo.org \
    --to=nightmorph@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