public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Puustinen, Ismo" <ismo.puustinen@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] python3: make readline, gdbm, and db support conditional.
Date: Thu, 8 Jun 2017 10:20:52 +0000	[thread overview]
Message-ID: <1496917250.23488.3.camel@intel.com> (raw)
In-Reply-To: <CAJTo0LbcEL78uNKy6CS0vUkDCT1OkW+X7ojk=KsYV-wTi-5S9Q@mail.gmail.com>

On Wed, 2017-06-07 at 15:10 +0100, Burton, Ross wrote:
> 
> On 7 June 2017 at 14:49, Ismo Puustinen <ismo.puustinen@intel.com>
> wrote:
> > +RRECOMMENDS_${PN}-core = "${@bb.utils.contains('PACKAGECONFIG',
> > 'readline', '${PN}-readline', '', d)}"
> > 
> 
> Recommends can not exists, so I wouldn't bother with this
> complication.

Ok, I'll remove it.

> > +RDEPENDS_${PN}-modules_remove += "${@bb.utils.contains('PACKAGECON
> > FIG', 'readline', '', '${PN}-readline', d)}"
> 
> (etc)
> 
> Don't use _remove and += as it's confusing.

I'll change that.

> But if for example readline is disabled, why would the package be
> created in the first place?

The package indeed isn't created. However, it's added to
RDEPENDS_python3-modules in python3 manifest file here:

https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devto
ols/python/python-3.5-manifest.inc#n280

The other variable changes are done also in the manifest. However, the
manifest file warns about modifying it, so the patch "reverses" the
changes based on PACKAGECONFIG from the recipe.

Ismo

  reply	other threads:[~2017-06-08 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 13:49 [PATCH v2] python3: make readline, gdbm, and db support conditional Ismo Puustinen
2017-06-07 14:10 ` Burton, Ross
2017-06-08 10:20   ` Puustinen, Ismo [this message]
2017-06-09  7:43   ` Puustinen, Ismo
2017-06-08 10:51 ` Alexander Kanavin
2017-06-08 12:35   ` Puustinen, Ismo
2017-06-08 12:37     ` Alexander Kanavin

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=1496917250.23488.3.camel@intel.com \
    --to=ismo.puustinen@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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