From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] gst-plugins-good: correctly handle gconf schema
Date: Thu, 20 Oct 2011 11:08:15 -0700 [thread overview]
Message-ID: <4EA0638F.4040708@linux.intel.com> (raw)
In-Reply-To: <FEAA96D9-206B-4993-B727-58BA40145FC4@dominion.thruhere.net>
On 10/20/2011 11:03 AM, Koen Kooi wrote:
> Op 20 okt. 2011 om 19:41 heeft Joshua Lock <josh@linux.intel.com> het volgende geschreven:
>
>>
>>
>> On 10/19/2011 10:41 PM, Koen Kooi wrote:
>>>
>>> Op 20 okt. 2011, om 00:49 heeft Joshua Lock het volgende geschreven:
>>>
>>>> Add the shipped gconf schema to the base package and inherit the gconf class
>>>> so that scheme processing is handled via post* scripts.
>>>>
>>>> Signed-off-by: Joshua Lock <josh@linux.intel.com>
>>>> ---
>>>> .../gstreamer/gst-plugins-good_0.10.30.bb | 6 ++++--
>>>> 1 files changed, 4 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb b/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb
>>>> index 96855aa..d63b09a 100644
>>>> --- a/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb
>>>> +++ b/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb
>>>> @@ -7,9 +7,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=a6f89e2100d9b6cdffcea4f398e37343 \
>>>>
>>>> DEPENDS += "gst-plugins-base gconf cairo jpeg libpng gtk+ zlib libid3tag flac \
>>>> speex libsoup-2.4 pulseaudio"
>>>> -PR = "r2"
>>>> +PR = "r3"
>>>>
>>>> -inherit gettext
>>>> +inherit gettext gconf
>>>>
>>>> EXTRA_OECONF += "--disable-aalib --disable-esd --disable-shout2 --disable-libcaca --disable-hal --without-check"
>>>>
>>>> @@ -20,3 +20,5 @@ do_configure_prepend() {
>>>>
>>>> SRC_URI[md5sum] = "62fd7a3ef187c4f99b3d7c352d58dae9"
>>>> SRC_URI[sha256sum] = "b12cba90b27d8423cd0a808939098d19db3996cfb9bf528507c6321782e095f6"
>>>> +
>>>> +FILES_${PN} += "${sysconfdir}/gconf/schemas/gstreamer-0.10.schemas"
>>>
>>> If think that schema needs to go into the gconf-elements plugin package, no?
>>
>> Is that a statement or a question? That was my hunch but I was having a
>> hard time finding anything which explicitly stated that.
>
> It was a question, there are few plugins that can hook into gconf, I lost track which plugins are in -good
OK, I don't know either. gconf-elements is a part of plugins-good and
some Makefile reading leads me to believe that the schema should be
shipped with that package.
Thanks Koen, updated pull request due shortly.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-10-20 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 22:49 [PATCH 0/4] Update tzdata and gst-plugins-good v2 Joshua Lock
2011-10-19 22:49 ` [PATCH 1/4] gst-plugins-good: update to 0.10.30 Joshua Lock
2011-10-19 22:49 ` [PATCH 2/4] tzdata: updated SRC_URI and update to 2011k Joshua Lock
2011-10-19 22:49 ` [PATCH 3/4] tzcode-native: update SRC_URI to new IANA location Joshua Lock
2011-10-19 22:49 ` [PATCH 4/4] gst-plugins-good: correctly handle gconf schema Joshua Lock
2011-10-20 5:41 ` Koen Kooi
2011-10-20 17:41 ` Joshua Lock
2011-10-20 18:03 ` Koen Kooi
2011-10-20 18:08 ` Joshua Lock [this message]
2011-10-20 17:15 ` [PATCH 0/4] Update tzdata and gst-plugins-good v2 Saul Wold
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=4EA0638F.4040708@linux.intel.com \
--to=josh@linux.intel.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