From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: saul.wold@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/5] packagegroups: Remove toolchain *-symlinks packages
Date: Fri, 28 Mar 2014 17:31:03 +0000 [thread overview]
Message-ID: <1396027863.14790.14.camel@ted> (raw)
In-Reply-To: <4691bff032d8536069f808068e5b477c8f47d213.1395996410.git.hongxu.jia@windriver.com>
On Fri, 2014-03-28 at 17:43 +0800, Hongxu Jia wrote:
> From: Mark Hatle <mark.hatle@windriver.com>
>
> We are no longer producing the *-symlinks packages, so remove the dependencies
> to those items.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb | 4 ----
> meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 4 ----
> 2 files changed, 8 deletions(-)
The binutils-symlinks package was removed however the gcc related ones
have not been. This patch is therefore not appropriate until that has
happened.
Cheers,
Richard
> diff --git a/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb b/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb
> index 74ed247..e21f8c1 100644
> --- a/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb
> +++ b/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb
> @@ -12,13 +12,9 @@ RDEPENDS_packagegroup-core-buildessential = "\
> autoconf \
> automake \
> binutils \
> - binutils-symlinks \
> cpp \
> - cpp-symlinks \
> gcc \
> - gcc-symlinks \
> g++ \
> - g++-symlinks \
> gettext \
> make \
> libstdc++ \
> diff --git a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
> index 8e3b917..5581d8e 100644
> --- a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
> +++ b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
> @@ -69,20 +69,16 @@ RDEPENDS_packagegroup-self-hosted-sdk = "\
> autoconf \
> automake \
> binutils \
> - binutils-symlinks \
> ccache \
> coreutils \
> cpp \
> - cpp-symlinks \
> distcc \
> eglibc-utils \
> eglibc-gconv-ibm850 \
> file \
> findutils \
> g++ \
> - g++-symlinks \
> gcc \
> - gcc-symlinks \
> intltool \
> ldd \
> less \
> --
> 1.8.1.2
>
next prev parent reply other threads:[~2014-03-28 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 9:43 [PATCH 0/5][Part IV] wr-misc patches Hongxu Jia
2014-03-28 9:43 ` [PATCH 1/5] kernel.bbclass: handles symbolic KERNEL_OUTPUT in bundle_initramfs task Hongxu Jia
2014-03-28 9:43 ` [PATCH 2/5] packagegroups: Remove toolchain *-symlinks packages Hongxu Jia
2014-03-28 17:31 ` Richard Purdie [this message]
2014-03-29 6:58 ` Hongxu Jia
2014-03-28 9:43 ` [PATCH 3/5] packagegroup-self-hosted: Use packagegroup-core-buildessential Hongxu Jia
2014-03-28 16:48 ` Iorga, Cristian
2014-03-31 8:31 ` Hongxu Jia
2014-03-31 8:52 ` Iorga, Cristian
2014-03-28 9:43 ` [PATCH 4/5] syslinux.bbclass: Enable additional kernel parameters for syslinux Hongxu Jia
2014-03-28 9:43 ` [PATCH 5/5] libc-common.bbclass: rename ALL the packages Hongxu Jia
2014-03-28 10:17 ` Martin Jansa
2014-03-28 10:28 ` Hongxu Jia
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=1396027863.14790.14.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox