From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Samuel Stirtzel <s.stirtzel@googlemail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Make pulseaudio a DISTRO_FEATURE
Date: Fri, 27 Jan 2012 10:54:31 +0000 [thread overview]
Message-ID: <2153827.uieeAmS9LV@helios> (raw)
In-Reply-To: <CAGiJk9fVik9Cc425O5kntWzgtf0Z2WPYnVcAjdTkswHY5YX7_Q@mail.gmail.com>
On Friday 27 January 2012 11:43:50 Samuel Stirtzel wrote:
> just a quick question, couldn't we use a separate recipe for phonon,
> so if a recipe depends on it we don't have to change distro vars?
Well, this thread is now about something more fundamental (how to introduce
new DISTRO_FEATURES), but we do still need to solve the problem that prompted
the wider discussion. It's still possible that someone would want to build
phonon without pulseaudio, even if it was split out into a separate recipe, so
I'm not sure that addresses the problem.
> IMHO it would be easier to just depend on libphonon.bb instead of
> adding a distro var for the one single recipe I'm working on.
> Just my 0.02 cents.
Pulseaudio has become an optional dependency for a lot of things. I think it
makes sense to make a decision on whether or not to include this on a distro
level since if you have it enabled in one place you almost certainly want it
enabled everywhere else (and disabled everywhere if it is disabled).
Now, at the start of this saga there was a question as to whether this should
be a DISTRO_FEATURE or PACKAGECONFIG (or both, ugh). Ultimately the result is
the same - distro policy controls whether this feature is on or off.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-27 11:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 15:32 [PATCH 0/3] Make pulseaudio a DISTRO_FEATURE Paul Eggleton
2011-11-23 15:32 ` [PATCH 1/3] default-distrovars: add pulseaudio to DISTRO_FEATURES Paul Eggleton
2011-11-23 15:32 ` [PATCH 2/3] qt4: make pulseaudio support conditional upon DISTRO_FEATURES Paul Eggleton
2011-11-23 15:32 ` [PATCH 3/3] gst-plugins-good: " Paul Eggleton
2011-11-23 15:59 ` [PATCH 0/3] Make pulseaudio a DISTRO_FEATURE Koen Kooi
2011-11-23 16:33 ` Paul Eggleton
2011-11-23 16:48 ` Phil Blundell
2011-11-23 17:09 ` Richard Purdie
2011-11-23 17:45 ` Paul Eggleton
2011-11-23 17:49 ` Paul Eggleton
2011-11-23 17:53 ` Phil Blundell
2011-11-23 18:22 ` Otavio Salvador
2011-12-29 12:55 ` Paul Eggleton
2012-01-16 17:58 ` Paul Eggleton
2012-01-16 18:12 ` Phil Blundell
2012-01-17 23:13 ` Process for New DISTRO_FEATURES (was: Re: [PATCH 0/3] Make pulseaudio a DISTRO_FEATURE) Richard Purdie
2012-01-17 20:02 ` [PATCH 0/3] Make pulseaudio a DISTRO_FEATURE Tom Rini
2012-01-27 10:43 ` Samuel Stirtzel
2012-01-27 10:54 ` Paul Eggleton [this message]
2012-01-27 11:34 ` Samuel Stirtzel
2012-01-27 12:13 ` Paul Eggleton
2012-01-28 20:05 ` Khem Raj
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=2153827.uieeAmS9LV@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=s.stirtzel@googlemail.com \
/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