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/3] Added multilib support for DEBIAN_NAME
Date: Fri, 16 Sep 2011 17:36:57 +0100 [thread overview]
Message-ID: <1316191025.20858.33.camel@ted> (raw)
In-Reply-To: <cover.1316177782.git.lianhao.lu@intel.com>
On Fri, 2011-09-16 at 21:01 +0800, Lianhao Lu wrote:
> This series of patches is meant to fix bug [YOCTO #1486].
>
> It added multilib support in package_name_hook() so MLPREFIX is kept in the
> package name after the debian package renaming.
>
> It changed the logic of multilib_sanity_check() that all the equal duplicated files
> from different multilib variants are allowed to be installed into the same rootfs.
>
> It also fixed several recipes to support the multilib in debian package renaming.
>
> The following changes since commit bb4dad44432b2e40ac3cf16baa45befbae3e70f5:
> Darren Hart (1):
> Prevent IMAGE_FEATURES from contaminating initrd
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib llu/bug1486
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/bug1486
>
> Lianhao Lu (3):
> debian/_ipk.bbclass: Added multilib support for package_name_hook()
> Misc: Added MLPREFIX to final pkg names in case of DEBIAN_NAMES.
> image/package.bbclass: Revise multilib support for DEBIAN_NAME.
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-09-16 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 13:01 [PATCH 0/3] Added multilib support for DEBIAN_NAME Lianhao Lu
2011-09-16 13:01 ` [PATCH 1/3] debian/_ipk.bbclass: Added multilib support for package_name_hook() Lianhao Lu
2011-09-16 13:01 ` [PATCH 2/3] Misc: Added MLPREFIX to final pkg names in case of DEBIAN_NAMES Lianhao Lu
2011-09-16 13:01 ` [PATCH 3/3] image/package.bbclass: Revise multilib support for DEBIAN_NAME Lianhao Lu
2011-09-16 16:36 ` Richard Purdie [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=1316191025.20858.33.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