Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <luca.boccassi@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] python3-pygobject: move python3-setuptools from RDEPENDS to DEPENDS
Date: Thu, 08 Aug 2019 14:57:37 +0100	[thread overview]
Message-ID: <f3afb57f910ef0b3d804ac4095d271ad7a2c8e57.camel@gmail.com> (raw)
In-Reply-To: <CANNYZj9NOARrMH8Vm1QXMwXzVUu7yTisK2X25jta_3xDCO0HeA@mail.gmail.com>

On Thu, 2019-08-08 at 14:03 +0200, Alexander Kanavin wrote:
> On Thu, 8 Aug 2019 at 13:47, <luca.boccassi@gmail.com> wrote:
> > -DEPENDS += "python3 glib-2.0"
> > +DEPENDS += "python3 python3-setuptools-native glib-2.0"
> 
> If this is required, then the build should fail, and it doesn't
> (neither on the autobuilder, nor in my local setup). Is this really
> needed? Does the build fail for you?
> 
> Alex

Hi,

You are right, it doesn't fail - upstream lists it as optional. I do
not know enough about this package to know how important it is - so
I'll send a v3 that just removes the RDEPENDS, which is the one thing I
cared about.

Thanks!

-- 
Kind regards,
Luca Boccassi



  reply	other threads:[~2019-08-08 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 10:52 [PATCH] python3-pygobject: move python3-setuptools from RDEPENDS to DEPENDS luca.boccassi
2019-08-05 11:32 ` Ross Burton
2019-08-08 11:47 ` [PATCH v2] " luca.boccassi
2019-08-08 12:03   ` Alexander Kanavin
2019-08-08 13:57     ` Luca Boccassi [this message]
2019-08-08 11:48 ` [PATCH] " Luca Boccassi
2019-08-08 13:58 ` [PATCH v3] " luca.boccassi
2019-08-08 14:03   ` Jacob Kroon
2019-08-08 14:37     ` Luca Boccassi
2019-08-08 14:02 ` [PATCH v4] python3-pygobject: remove python3-setuptools from RDEPENDS luca.boccassi

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=f3afb57f910ef0b3d804ac4095d271ad7a2c8e57.camel@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=alex.kanavin@gmail.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