From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] multilib related fixed for opkg backend
Date: Mon, 22 Aug 2011 15:38:26 -0700 [thread overview]
Message-ID: <4E52DA62.2010205@linux.intel.com> (raw)
In-Reply-To: <cover.1313484812.git.lianhao.lu@intel.com>
On 08/16/2011 01:56 AM, Lianhao Lu wrote:
> This patch fixed the bug #1345 to allow the opkg backend installing both
> normal pacakges and multilib packages into the same rootfs.
>
> The following changes since commit 13db5f420ca9bff98561f80d78958278734ad1f4:
> Zhai Edwin (1):
> distro-tracking: Update info for gpgme, libassuan, apr... after last upgrade.
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib llu/bug1345
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/bug1345
>
> Lianhao Lu (1):
> package(_ipk).bbclass: opkg using ALL_MULTILIB_PACKAGE_ARCHS
>
> meta/classes/package.bbclass | 13 ++-----------
> meta/classes/package_ipk.bbclass | 30 ++++++++----------------------
> meta/classes/utils.bbclass | 24 +++++++++++++++++++-----
> 3 files changed, 29 insertions(+), 38 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-08-22 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 8:56 [PATCH 0/1] multilib related fixed for opkg backend Lianhao Lu
2011-08-16 8:56 ` [PATCH 1/1] package(_ipk).bbclass: opkg using ALL_MULTILIB_PACKAGE_ARCHS Lianhao Lu
2011-08-22 22:38 ` Saul Wold [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=4E52DA62.2010205@linux.intel.com \
--to=sgw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.