All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Lianhao Lu <lianhao.lu@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/5] [BUG# 227] rpm/deb support for meta-toolchain.
Date: Sat, 29 Jan 2011 13:28:07 +0000	[thread overview]
Message-ID: <1296307687.13501.4152.camel@rex> (raw)
In-Reply-To: <cover.1296208216.git.lianhao.lu@intel.com>

On Fri, 2011-01-28 at 18:01 +0800, Lianhao Lu wrote:
> From: Lianhao Lu <lianhao.lu@intel.com>
> 
> The purpose of this series of patches is to add rpm/deb support in meta-toolchain creation,
> and also to fix bug #227.
> 
> It makes the task populate_sdk in meta/recipes-core/meta/meta-toolchain.bb more generic
> to support installing packages from ipk, rpm, and deb files in creating meta-toolchain 
> tarball, and move the populate_sdk task out of meta-toolchain.bb recipe into a bbclass.
> 
> It added populate_sdk_xxx.bbclass for different package file format.
> 
> Since there are quite many code duplication between relevant popuplage_sdk_xxx and rootfs_xxx 
> bbclasses, it also moved the common code into the package_xxx.bbclass, based on RP's suggestion. 
> The generic function package_install_internal_xxx() may installs a list of packages, based on the
> information specified by various shell environment variables about where the target directory to
> be installed to, package architecture information, etc.
> 
> It also fixed a bug in cross-canadian.bbclass to enable the package_deb.bbclass generate correct
> deb package files for cross-canadian recipies.

These patches are good, if you have time could you:

a) rebase these patches against the merged rpm changes from Mark Hatle 
   from the rpm update to 5.4

b) Try hard to split out any logical changes you can from the bigger
patches into specific steps. For example, enhancing the log_check
function and moving those around could be a separate commit.

The idea is to make changes in clear logical steps where at all possible
so anyone reviewing the changes (such as Saul, Mark and myself) can then
more quickly "see" the changes are correct and also, if there are
problems, we can bisect the commits to track down which change the
problem is from.

Cheers,

Richard





  parent reply	other threads:[~2011-01-29 13:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 10:01 [PATCH 0/5] [BUG# 227] rpm/deb support for meta-toolchain Lianhao Lu
2011-01-28 10:01 ` [PATCH 1/5] cross-canadian.bbclass: Correct deb package arch Lianhao Lu
2011-01-28 17:01   ` Richard Purdie
2011-01-28 10:01 ` [PATCH 2/5] apt-native: Added licence checksum Lianhao Lu
2011-01-28 17:01   ` Richard Purdie
2011-01-28 10:01 ` [PATCH 4/5] classes/populate_sdk_xxx.bbclass: pkg format support for populate_sdk task Lianhao Lu
2011-01-28 10:01 ` [PATCH 5/5] meta-toolchain: pkg format independant " Lianhao Lu
2011-01-28 10:01 ` [PATCH 3/5] image/rootfs_xx/package_xx.bbclass: prepare to add " Lianhao Lu
2011-01-29 13:28 ` Richard Purdie [this message]
2011-01-30  8:23   ` [PATCH 0/5] [BUG# 227] rpm/deb support for meta-toolchain Lu, Lianhao

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=1296307687.13501.4152.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=lianhao.lu@intel.com \
    --cc=poky@yoctoproject.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.