Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] rootfs generation improvements
Date: Mon, 23 Jul 2012 11:29:26 +0100	[thread overview]
Message-ID: <1532317.TE5c1Jzpbs@helios> (raw)
In-Reply-To: <50058C43.7090105@linux.intel.com>

On Tuesday 17 July 2012 09:01:07 Saul Wold wrote:
> On 07/11/2012 06:04 AM, Paul Eggleton wrote:
> > Fix up handling of "complementary" package installation (dev, dbg, doc,
> > etc.) and introduce a staticdev-pkgs IMAGE_FEATURES feature.
> > 
> > I've tested this with all backends using buildhistory to examine the
> > changes to the image contents, and compared the lists of files in the
> > SDK-from-image output with the rpm backend. Unfortunately it does
> > increase the do_rootfs time slightly; one of my next tasks will be to
> > try to do some optimisation here.
> > 
> > The following changes since commit 
b76a7bc8dcb7aed7d6f026e77a226837004c50af:
> >    libgomp: add libgomp (openmp) library, and build for powerpc targets by
> >    default (2012-07-11 11:35:16 +0100)> 
> > are available in the git repository at:
> >    git://git.openembedded.org/openembedded-core-contrib paule/rootfs
> >    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=
> >    paule/rootfs> 
> > Paul Eggleton (3):
> >    classes/rootfs_deb: use more reliable check for package existence
> 
> Merged this one into OE-Core
> 
> >    Rework installation of dev, dbg, doc, and locale packages
> >    classes/image: add staticdev-pkgs IMAGE_FEATURES feature
> 
> There was an issue with either one or both of these during build
> testing, I know you are looking into it.

Indeed, this triggered some kind of environment size limit and has exposed a 
few other lurking issues as well. It also failed to handle debian package 
renaming. I have a reworked and extended patchset coming, please disregard the 
unmerged part of this one.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-07-23 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 13:04 [PATCH 0/3] rootfs generation improvements Paul Eggleton
2012-07-11 13:04 ` [PATCH 1/3] classes/rootfs_deb: use more reliable check for package existence Paul Eggleton
2012-07-11 13:04 ` [PATCH 2/3] Rework installation of dev, dbg, doc, and locale packages Paul Eggleton
2012-07-11 13:04 ` [PATCH 3/3] classes/image: add staticdev-pkgs IMAGE_FEATURES feature Paul Eggleton
2012-07-17 16:01 ` [PATCH 0/3] rootfs generation improvements Saul Wold
2012-07-23 10:29   ` Paul Eggleton [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=1532317.TE5c1Jzpbs@helios \
    --to=paul.eggleton@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