From: Adrian Bunk <bunk@stusta.de>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 01/13] python: update to 2.7.17
Date: Mon, 25 Nov 2019 05:36:07 +0200 [thread overview]
Message-ID: <20191125033607.GB16252@localhost> (raw)
In-Reply-To: <f63e4c7f-c961-453a-ba91-5175675829b2@intel.com>
On Wed, Nov 20, 2019 at 11:57:47AM +0000, Ross Burton wrote:
> On 19/11/2019 16:30, Adrian Bunk wrote:
> > You want meta-oe to have a LAYERDEPENDS on a new python2 layer that is
> > not in meta-openembedded?
>
> Would that be a bad thing? Layers shouldn't care about where they are
> hosted.
Hosting is less of a problem than maintainership and quality.
And when something isn't good enough for inclusion in meta-oe then
meta-oe shouldn't depend on it.
> My ideal would be that meta-python2 exists with both the python2 recipes and
> all of the py2 parts of meta-python. Until meta-oe is Py3-only, it can
> either depend on this layer or recipes are blacklisted unless the layer is
> present.
Layer dependencies are not transparent, a dependency means all users
have to add meta-python2 to bblayers.conf.
> Ross
cu
Adrian
next prev parent reply other threads:[~2019-11-25 3:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 13:07 [PATCH 01/13] python: update to 2.7.17 Alexander Kanavin
2019-11-18 13:07 ` [PATCH 02/13] runqemu: add options that enable virgl with the SDL frontend Alexander Kanavin
2019-11-18 13:07 ` [PATCH 03/13] oe-selftest: extend virgl gtk test to also check the SDL option Alexander Kanavin
2019-11-18 13:07 ` [PATCH 04/13] tiff: update to 4.1.0 Alexander Kanavin
2019-11-18 13:07 ` [PATCH 05/13] librepo: upgrade 1.10.6 -> 1.11.0 Alexander Kanavin
2019-11-18 13:07 ` [PATCH 06/13] btrfs-tools: upgrade 5.3 -> 5.3.1 Alexander Kanavin
2019-11-18 13:07 ` [PATCH 07/13] psmisc: update to 23.3 Alexander Kanavin
2019-11-18 13:07 ` [PATCH 08/13] libxslt: update to 1.1.34 Alexander Kanavin
2019-11-18 13:07 ` [PATCH 09/13] Revert "devtool/standard.py: Not filtering devtool workspace for devtool finish" Alexander Kanavin
2019-11-18 13:07 ` [PATCH 10/13] mpg123: upgrade 1.25.12 -> 1.25.13 Alexander Kanavin
2019-11-18 13:07 ` [PATCH 11/13] vala: upgrade 0.46.3 -> 0.46.4 Alexander Kanavin
2019-11-18 13:08 ` [PATCH 12/13] systat: upstream version check is working again Alexander Kanavin
2019-11-18 13:47 ` Peter Kjellerstedt
2019-11-18 13:08 ` [PATCH 13/13] man-pages: correct the SRC_URI Alexander Kanavin
2019-11-18 13:31 ` ✗ patchtest: failure for "python: update to 2.7.17..." and 12 more Patchwork
2019-11-18 18:13 ` [PATCH 01/13] python: update to 2.7.17 Khem Raj
2019-11-18 21:05 ` Adrian Bunk
2019-11-18 21:39 ` Khem Raj
2019-11-18 22:06 ` Adrian Bunk
2019-11-18 22:16 ` Khem Raj
2019-11-18 22:34 ` Ross Burton
2019-11-18 22:55 ` Adrian Bunk
2019-11-18 23:26 ` Khem Raj
2019-11-19 7:57 ` Tim Orling
2019-11-19 11:30 ` Alexander Kanavin
2019-11-19 15:49 ` Khem Raj
2019-11-19 16:30 ` Adrian Bunk
2019-11-19 16:47 ` Khem Raj
2019-11-20 11:57 ` Ross Burton
2019-11-25 3:36 ` Adrian Bunk [this message]
2019-11-19 22:44 ` Andreas Müller
2019-11-30 9:49 ` Adrian Bunk
2019-11-19 11:24 ` Alexander Kanavin
2019-11-20 12:56 ` Tom Rini
2019-11-20 13:47 ` Alexander Kanavin
2019-11-20 13:50 ` Tom Rini
2019-11-20 15:06 ` Alexander Kanavin
2019-11-20 15:08 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2019-11-18 14:28 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=20191125033607.GB16252@localhost \
--to=bunk@stusta.de \
--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