Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Colin Walters <walters@verbum.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Add packagegroup-core-buildessential
Date: Thu, 18 Oct 2012 12:50:14 -0700	[thread overview]
Message-ID: <50805D76.8090103@linux.intel.com> (raw)
In-Reply-To: <1348530882.25427.1.camel@lenny>

On 09/24/2012 04:54 PM, Colin Walters wrote:
> [Not heavily tested, but sent for discussion]
>
> task-core-sdk is too big - for example, I simply don't want to ship tcl, ever =)
> Historically distcc caused a large dependency graph explosion because it has
> a utility which uses gtk+, although that was fixed.
>
> packagegroup-core-sdk also includes coreutils, which is a bit
> confusing; conceptually things dependent on coreutils should pull it
> in explicitly, or possibly we just declare coreutils to be in the
> minimal build set.
>
> So packagegroup-core-buildessential is intended to be similar to
> Debian's "build-essential" package.  It's the stuff needed by say 80+%
> of components, not worth repeating over and over.
>
> Signed-off-by: Colin Walters <walters@verbum.org>
> ---
>   .../packagegroup-core-buildessential.bb            | 30 ++++++++++++++++++++++
>   .../packagegroups/packagegroup-core-sdk.bb         | 17 +-----------
>   2 files changed, 31 insertions(+), 16 deletions(-)
>   create mode 100644 meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb
>
>
Merged into OE-Core

Thanks
	Sau!

>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



      parent reply	other threads:[~2012-10-18 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 23:54 [PATCH] Add packagegroup-core-buildessential Colin Walters
2012-09-25  9:37 ` Burton, Ross
2012-10-18 19:50 ` 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=50805D76.8090103@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=walters@verbum.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