public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrii Bordunov <aborduno@cisco.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: allow using EXCLUDE_FROM_SHLIBS for subpackages
Date: Wed, 16 Nov 2016 10:47:45 +0000	[thread overview]
Message-ID: <1479293265.28508.4.camel@linuxfoundation.org> (raw)
In-Reply-To: <1476118955-12401-1-git-send-email-aborduno@cisco.com>

On Mon, 2016-10-10 at 20:02 +0300, Andrii Bordunov wrote:
> Some packages containing shared libraries might be registered
> as shlib providers when they shouldn't (for example, the lib is for
> their private use and must not generate any dependency).
> 
> EXCLUDE_FROM_SHLIBS is targeted at that, but it could be set
> for entire recipe only.
> 
> This patch expands EXCLUDE_FROM_SHLIBS usage, so now it's possible
> to set it in a style similar with RDEPENDS. For example:
>  EXCLUDE_FROM_SHLIBS_${PN}-ptest = "1"
> 
> Signed-off-by: Andrii Bordunov <aborduno@cisco.com>
> ---
>  meta/classes/package.bbclass | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)

My main concern here is actually performance. For a package with many
sub packages you just added many calls to getVar when that getVar is
extremely unlikely to find any value. Whilst not hugely slow, that
operation isn't trivial and hard to fix later.

I'm wondering if we could support the syntax

EXCLUDE_FROM_SHLIBS = "${PN}-ptest"

and then have "1", used in a couple of places as the special value to
mean all packages?

Also please use False, not 0 as the parameter to getVar.

Cheers,

Richard



  parent reply	other threads:[~2016-11-16 10:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 17:02 [PATCH] package.bbclass: allow using EXCLUDE_FROM_SHLIBS for subpackages Andrii Bordunov
2016-10-19 13:58 ` Andrii Bordunov
2016-11-15 15:05   ` Andrii Bordunov
2016-11-16 10:29     ` Burton, Ross
2016-11-16 10:47 ` Richard Purdie [this message]
2017-03-16 15:07   ` Andrii Bordunov
2018-03-13 17:25     ` [PATCH v3] " Andrii Bordunov
2018-04-12 14:42       ` Andrii Bordunov
2018-06-11 12:20         ` Andrii Bordunov
2018-06-16 12:00           ` Richard Purdie

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=1479293265.28508.4.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=aborduno@cisco.com \
    --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