Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gstreamer: make pulseaudio support dependent on DISTRO_FEATURES
Date: Wed, 26 Sep 2012 14:45:58 +0100	[thread overview]
Message-ID: <1873147.GujWgbYhhC@helios> (raw)
In-Reply-To: <20120926133013.GM3313@jama.jama.net>

On Wednesday 26 September 2012 15:30:13 Martin Jansa wrote:
> On Wed, Sep 26, 2012 at 02:24:07PM +0100, Paul Eggleton wrote:
> > On Wednesday 26 September 2012 14:32:57 Martin Jansa wrote:
> > > On Wed, Sep 26, 2012 at 01:31:10PM +0100, Paul Eggleton wrote:
> > > > On Wednesday 26 September 2012 13:38:19 Martin Jansa wrote:
> > > > > On Wed, Sep 26, 2012 at 12:34:05PM +0100, Paul Eggleton wrote:
> > > > > > This should be no change to the previous situation unless you
> > > > > > explicitly have pulseaudio in DISTRO_FEATURES_BACKFILL_CONSIDERED
> > > > > > (currently).
> > > > > 
> > > > > Why not use PACKAGECONFIG for this?
> > > > 
> > > > Only because I didn't see the need complicate it just to be able to
> > > > configure it on a per-recipe basis - you almost certainly want
> > > > pulseaudio
> > > > either on or off everywhere. If you want it for stylistic reasons,
> > > > sure,
> > > > I guess... it is a bit ugly though.
> > > 
> > > Well it looked to me like ideal use-case for PACKAGECONFIG.
> > 
> > It does encapsulate the DEPENDS and EXTRA_OECONF into one piece, yes, but
> > then when you make the PACKAGECONFIG option set from DISTRO_FEATURES
> > anyway it gets ugly, and here I'm not convinced it adds anything useful.
> 
> Yes, but that's the case for almost every other PACKAGECONFIG use in
> oe-core too AFAIK and I was asked to convert similar commit to use
> PACKAGECONFIG before so I was expecting that the ultimate goal is to
> replace all such DISTRO_FEATURE tests with PACKAGECONFIG where possible,
> not to add more of them.

Perhaps. Well, I just noticed I need to correct the commit message anyway 
(it's a change to gst-plugins-good, not gstreamer) so given that I'll send a 
v2 using PACKAGECONFIG.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-09-26 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 11:34 [PATCH] gstreamer: make pulseaudio support dependent on DISTRO_FEATURES Paul Eggleton
2012-09-26 11:38 ` Martin Jansa
2012-09-26 12:31   ` Paul Eggleton
2012-09-26 12:32     ` Martin Jansa
2012-09-26 13:24       ` Paul Eggleton
2012-09-26 13:30         ` Martin Jansa
2012-09-26 13:45           ` Paul Eggleton [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=1873147.GujWgbYhhC@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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