From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] classes/[gnome|gnomebase|mime]: enhance gnome related classes
Date: Wed, 09 Nov 2011 11:14:57 -0800 [thread overview]
Message-ID: <4EBAD131.1040000@linux.intel.com> (raw)
In-Reply-To: <8EF5D367-6159-471F-8F2C-F3FA3216F05D@dominion.thruhere.net>
On 09/11/11 01:27, Koen Kooi wrote:
>
> Op 9 nov. 2011, om 01:53 heeft Joshua Lock het volgende geschreven:
>
>> This patch pulls in the gnome related classes from oe-core which
>> adds extra packaging rules and functionality whilst modularising things
>> so that one can get a subset of gnome functionality without adding a lot
>> of extra dependencies.
>>
>> These aren't an exact copy of the classes from meta-openembedded, notable
>> differences are:
>> * gnome.bbclass - I dropped the BBCLASSEXTEND
>
> It looks that will break a number of things in meta-oe, why was it dropped?
Richard didn't want us to add native variants of everything that uses
the gnome class.
At least in the short term it should be easy enough to keep meta-oe's
gnome.bbclass where the BBCLASSEXTEND is still set.
Whether you'd want to keep that or instead set BBCLASSEXTEND in the
required places feels like a policy decision for meta-oe.
>> * mime.bbclass:
>> - updated coding style
>> - use which to find update-mime-database program rather than hard coded
>> - fix typo in populate_packges_append such that it's actually called
>
> Will it drag in the shared-mime-info-data package you created automatically now?
>
> Also, do you have matching patches to update meta-oe now that these things are heading into oe-core?
I have not, I wanted to see what the feedback on this series was.
Particularly the BBCLASSEXTEND bit as above.
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-09 19:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 0:53 [PATCH 0/3] Switch to upstream GConf Joshua Lock
2011-11-09 0:53 ` [PATCH 1/3] shared-mime-info: package runtime data separately Joshua Lock
2011-11-18 12:20 ` Rainer Koenig
2011-11-23 21:45 ` Khem Raj
2011-11-23 21:59 ` Koen Kooi
2011-11-09 0:53 ` [PATCH 2/3] classes/[gnome|gnomebase|mime]: enhance gnome related classes Joshua Lock
2011-11-09 9:27 ` Koen Kooi
2011-11-09 9:37 ` Richard Purdie
2011-11-09 10:27 ` Koen Kooi
2011-11-09 10:35 ` Richard Purdie
2011-11-09 11:18 ` Koen Kooi
2011-11-09 20:20 ` Joshua Lock
2011-11-09 19:14 ` Joshua Lock [this message]
2011-11-09 0:53 ` [PATCH 3/3] gconf: add upstream GNOME gconf 3.2.3 and drop gconf-dbus Joshua Lock
2011-11-09 15:18 ` Richard Purdie
2011-11-10 12:26 ` [PATCH 0/3] Switch to upstream GConf Richard Purdie
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=4EBAD131.1040000@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