Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] Add packagegroup-core-buildessential
Date: Mon, 24 Sep 2012 19:54:42 -0400	[thread overview]
Message-ID: <1348530882.25427.1.camel@lenny> (raw)

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

[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



[-- Attachment #2: 0001-Add-packagegroup-core-buildessential.patch --]
[-- Type: text/x-patch, Size: 2981 bytes --]

From 80a199a2fd34cca08324f228fc1272086a476e61 Mon Sep 17 00:00:00 2001
From: Colin Walters <walters@verbum.org>
Date: Mon, 24 Sep 2012 19:46:01 -0400
Subject: [PATCH] Add packagegroup-core-buildessential

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

diff --git a/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb b/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb
new file mode 100644
index 0000000..164da36
--- /dev/null
+++ b/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb
@@ -0,0 +1,30 @@
+#
+# Copyright (C) 2007 OpenedHand Ltd.
+# Copyright (C) 2012 Red Hat, Inc.
+#
+
+SUMMARY = "Essential build dependencies"
+LICENSE = "MIT"
+PR = "r0"
+
+inherit packagegroup
+
+RDEPENDS_packagegroup-core-buildessential = "\
+    autoconf \
+    automake \
+    binutils \
+    binutils-symlinks \
+    cpp \
+    cpp-symlinks \
+    gcc \
+    gcc-symlinks \
+    g++ \
+    g++-symlinks \
+    gettext \
+    make \
+    libstdc++ \
+    libstdc++-dev \
+    libtool \
+    pkgconfig \
+    "
+
diff --git a/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb b/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
index b00bf07..985bebd 100644
--- a/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
@@ -16,28 +16,13 @@ RREPLACES_packagegroup-core-sdk = "task-core-sdk"
 RCONFLICTS_packagegroup-core-sdk = "task-core-sdk"
 
 RDEPENDS_packagegroup-core-sdk = "\
-    autoconf \
-    automake \
-    binutils \
-    binutils-symlinks \
+    packagegroup-core-buildessential \
     coreutils \
-    cpp \
-    cpp-symlinks \
     ccache \
     diffutils \
-    gcc \
-    gcc-symlinks \
-    g++ \
-    g++-symlinks \
-    gettext \
-    make \
     intltool \
-    libstdc++ \
-    libstdc++-dev \
-    libtool \
     perl-module-re \
     perl-module-text-wrap \
-    pkgconfig \
     findutils \
     quilt \
     less \
-- 
1.7.11.4


             reply	other threads:[~2012-09-25  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 23:54 Colin Walters [this message]
2012-09-25  9:37 ` [PATCH] Add packagegroup-core-buildessential Burton, Ross
2012-10-18 19:50 ` Saul Wold

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=1348530882.25427.1.camel@lenny \
    --to=walters@verbum.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