From: Luca Boccassi <luca.boccassi@gmail.com>
To: Jacob Kroon <jacob.kroon@mikrodidakt.se>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] python3-pygobject: move python3-setuptools from RDEPENDS to DEPENDS
Date: Thu, 08 Aug 2019 15:37:04 +0100 [thread overview]
Message-ID: <9ff85acd1d43d6003ea5fd53e0701a08b3fedfd1.camel@gmail.com> (raw)
In-Reply-To: <81efba6d-0174-370f-778c-c4c6fa434afc@mikrodidakt.se>
On Thu, 2019-08-08 at 14:03 +0000, Jacob Kroon wrote:
> Hi Luca,
>
> On 8/8/19 3:58 PM,
> luca.boccassi@gmail.com
> wrote:
> > From: Luca Boccassi <
> > luca.boccassi@microsoft.com
> > >
> >
> > python3-setuptools is necessary to build pygobject but not to run
> > it, as
> > also documented by the upstream packaging guide:
> >
> > https://gitlab.gnome.org/GNOME/pygobject/blob/master/docs/packagingguide.rst
> >
> >
> > Move it to DEPENDS to shrink the runtime dependency chain, as
> > setuptools
> > includes scripts to download other packages, which might not be
> > desired on
> > a minimal image.
> >
>
> This commmit message should be rephrased now.
> /Jacob
Hi,
Yes I realised 0.1 seconds after git send-email completed :-) Already
sent v4:
https://patchwork.openembedded.org/patch/163798/
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-08-08 14:37 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
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 [this message]
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=9ff85acd1d43d6003ea5fd53e0701a08b3fedfd1.camel@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=jacob.kroon@mikrodidakt.se \
--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