Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] task-core-lsb: Don't pull in eglibc-pic via RDEPENDS
Date: Wed, 15 Aug 2012 14:51:14 +0100	[thread overview]
Message-ID: <1345038674.538.19.camel@ted> (raw)
In-Reply-To: <1344984262-31589-1-git-send-email-andy.ross@windriver.com>

On Tue, 2012-08-14 at 15:44 -0700, Andy Ross wrote:
> The task-core-lsb-runtime-add subpackage includes eglibc-pic as an
> RDEPEND.  That's incorrect, eglibc-pic is nothing but 22MB of static
> libraries and should never appear as a runtime dependency.
> 
> Signed-off-by: Andy Ross <andy.ross@windriver.com>
> ---
>  meta/recipes-extended/tasks/task-core-lsb.bb | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/meta/recipes-extended/tasks/task-core-lsb.bb b/meta/recipes-extended/tasks/task-core-lsb.bb
> index 553b89e..be9eac2 100644
> --- a/meta/recipes-extended/tasks/task-core-lsb.bb
> +++ b/meta/recipes-extended/tasks/task-core-lsb.bb
> @@ -194,7 +194,6 @@ RDEPENDS_task-core-lsb-runtime-add = "\
>      eglibc-localedata-posix \
>      eglibc-extra-nss \
>      eglibc-pcprofile \
> -    eglibc-pic \
>      eglibc-utils \
>  "

Are files in that package required in order to pass LSB tests?

I'm fine with removing it if it isn't required but I would like that
confirmation before we merge this.

Cheers,

Richard




  parent reply	other threads:[~2012-08-15 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 22:44 [PATCH] task-core-lsb: Don't pull in eglibc-pic via RDEPENDS Andy Ross
2012-08-15  7:38 ` Koen Kooi
2012-08-15 15:58   ` Andy Ross
2012-08-15 15:58     ` Andy Ross
2012-08-15 13:51 ` Richard Purdie [this message]
2012-08-15 15:37   ` Andy Ross
2012-08-15 15:41     ` Phil Blundell

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=1345038674.538.19.camel@ted \
    --to=richard.purdie@linuxfoundation.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