From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7][PULL] Hob2 related oe-core changes
Date: Fri, 06 Jan 2012 16:27:47 +0000 [thread overview]
Message-ID: <1325867267.14746.8.camel@ted> (raw)
In-Reply-To: <cover.1325840092.git.dongxiao.xu@intel.com>
On Fri, 2012-01-06 at 17:04 +0800, Dongxiao Xu wrote:
> Hi Richard,
>
> This pull request is the hob2 related oe-core changes.
> Please help to review and pull.
>
> Note that this pull request has dependency on the hob related bitbake changes.
>
> Thanks,
> Dongxiao
>
> The following changes since commit 4a85312568a6bb052cc511c15b4ae842ff7f8e59:
> Richard Purdie (1):
> image-mklibs/package_ipk: Remove bashisms
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib dxu4/hob-oecore-changes
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/hob-oecore-changes
>
> Dongxiao Xu (6):
> bblayers.conf.sample: Use ?= to set BBLAYERS
> image.bbclass: Use ?= to set LINGUAS_INSTALL
I merged these.
> packageinfo.bbclass: add a new bbclass to pass package information
I still have quite a strong dislike of this code, its rather nasty to
require this and I wish we could come up with a less ugly way to collect
up this information.
> hob.bb: Add a empty image template
> hob-toolchain: add a new recipe hob-toolchain
> layers: add a new folder to put user added layers
I don't like these three. They're horribly hob specific and IMO
shouldn't be in the general metadata. If there is no way to avoid them,
they should perhaps go into a meta-hob layer directory to keep them
separate from the rest of the system.
I'm still puzzled how the layers directory helps. We deliberately
support generic layer locations so forcing the user to place them in a
particular place seems like a bit of a backwards step? :/.
Cheers,
Richard
next prev parent reply other threads:[~2012-01-06 16:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 9:04 [PATCH 0/7][PULL] Hob2 related oe-core changes Dongxiao Xu
[not found] ` <cover.1325840474.git.dongxiao.xu@intel.com>
2012-01-06 9:04 ` [PATCH 1/7] bblayers.conf.sample: Use ?= to set BBLAYERS Dongxiao Xu
2012-01-06 9:05 ` [PATCH 2/7] image.bbclass: Use ?= to set LINGUAS_INSTALL Dongxiao Xu
2012-01-06 9:05 ` [PATCH 3/7] package.bbclass: set package size into pkgdata for hob2's use Dongxiao Xu
2012-01-06 9:05 ` [PATCH 4/7] packageinfo.bbclass: add a new bbclass to pass package information Dongxiao Xu
2012-01-06 10:32 ` Koen Kooi
2012-01-07 8:00 ` Xu, Dongxiao
2012-01-06 9:05 ` [PATCH 5/7] hob.bb: Add a empty image template Dongxiao Xu
2012-01-06 9:05 ` [PATCH 6/7] hob-toolchain: add a new recipe hob-toolchain Dongxiao Xu
2012-01-06 9:05 ` [PATCH 7/7] layers: add a new folder to put user added layers Dongxiao Xu
2012-01-06 16:27 ` Richard Purdie [this message]
2012-01-06 16:37 ` [PATCH 0/7][PULL] Hob2 related oe-core changes Mark Hatle
2012-01-06 16:41 ` Koen Kooi
2012-01-07 7:47 ` Xu, Dongxiao
2012-01-07 7:53 ` Xu, Dongxiao
2012-01-07 7:40 ` Xu, Dongxiao
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=1325867267.14746.8.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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