All of lore.kernel.org
 help / color / mirror / Atom feed
From: ronunes@gmail.com
To: meta-freescale@yoctoproject.org
Cc: Rogerio Nunes <rogerio.nunes@freescale.com>
Subject: [meta-fsl-demos][PATCH 0/3] packagegroup refactoring
Date: Fri, 24 Jan 2014 18:45:46 -0500	[thread overview]
Message-ID: <1390607149-1853-1-git-send-email-ronunes@gmail.com> (raw)

From: Rogerio Nunes <rogerio.nunes@freescale.com>

This patchset refactors the packagegroup recipe, spliting it in
smaller recipes.

With this approach, it will be easier to organize the inclusion of
more packagegroups, and also to re-organize packages already
grouped in one of the current groups.

This is not only about code refactoring tough.
We will have better scalablity also in build time.

When a single packagegroup from a recipe that includes multiple
packagegroups is added to one image, all the tasks to build all
the packages from the same recipe file are added to the execution
queue. In other words, if you need only one of the packagegroups
from a big recipe file in your image, currently you are paying
a high price in terms of build time for this convenience.

Longer term, I hope we will be able to have a better set of reference
images in this layer, from small ones that can be built faster, to
more complete images full of features.

Regards.

Rogerio Nunes (3):
  packagegroup: rename to packagegroups
  packagegroup-fsl: split packagegroup into multiple recipes
  packagegroup-fsl-tools-testapps: Use amd-gpu-x11-bin-mx51 only with
    X11

 recipes-fsl/packagegroup/packagegroup-fsl.bb       | 89 ----------------------
 .../packagegroups/packagegroup-fsl-gstreamer.bb    | 33 ++++++++
 .../packagegroup-fsl-tools-benchmark.bb            | 20 +++++
 .../packagegroup-fsl-tools-testapps.bb             | 45 +++++++++++
 4 files changed, 98 insertions(+), 89 deletions(-)
 delete mode 100644 recipes-fsl/packagegroup/packagegroup-fsl.bb
 create mode 100644 recipes-fsl/packagegroups/packagegroup-fsl-gstreamer.bb
 create mode 100644 recipes-fsl/packagegroups/packagegroup-fsl-tools-benchmark.bb
 create mode 100644 recipes-fsl/packagegroups/packagegroup-fsl-tools-testapps.bb

-- 
1.8.3.2



             reply	other threads:[~2014-01-24 23:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 23:45 ronunes [this message]
2014-01-24 23:45 ` [meta-fsl-demos][PATCH 1/3] packagegroup: rename to packagegroups ronunes
2014-01-25 13:39   ` Fabio Estevam
2014-01-25 18:53     ` Rogerio Nunes
2014-01-25 19:15   ` Daiane Angolini
2014-01-24 23:45 ` [meta-fsl-demos][PATCH 2/3] packagegroup-fsl: split packagegroup into multiple recipes ronunes
2014-01-25 19:21   ` Daiane Angolini
2014-01-25 20:23     ` Rogerio Nunes
2014-01-25 21:51       ` Otavio Salvador
2014-01-24 23:45 ` [meta-fsl-demos][PATCH 3/3] packagegroup-fsl-tools-testapps: Use amd-gpu-x11-bin-mx51 only with X11 ronunes
2014-01-25 18:48   ` Otavio Salvador
2014-01-25 18:49     ` Otavio Salvador
2014-01-25 18:57       ` Rogerio Nunes
2014-01-25 19:12 ` [meta-fsl-demos][PATCH 0/3] packagegroup refactoring Daiane Angolini

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=1390607149-1853-1-git-send-email-ronunes@gmail.com \
    --to=ronunes@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=rogerio.nunes@freescale.com \
    /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.