From: akuster <akuster@mvista.com>
To: "Jan-Simon Möller" <dl9pf@gmx.de>,
openembedded-architecture@lists.openembedded.org
Cc: Philip Balister <philip@balister.org>,
bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Python 3 for Bitbake
Date: Thu, 5 May 2016 10:50:27 -0700 [thread overview]
Message-ID: <572B87E3.9020105@mvista.com> (raw)
In-Reply-To: <9084039.ulb8Qqh204@elrond>
On 05/05/2016 10:29 AM, Jan-Simon Möller wrote:
> Am Donnerstag, 5. Mai 2016, 10:13:21 schrieb Mark Hatle:
>>>> Question, do we need any type of identifier in layers to say they're
>>>> "python3" compatible or not?
>>>
>>> Layers that are python2 will need krogoth branches. I'd expect master
>>> branches to follow oe-core/master and jump to python3.
>>
>> I don't disagree, but my experience has been that branching is late or never
>> in a lot of layers.
>>
>> This might be a place where we need to plan to go through the layer index
>> and at least see if the layer parses -- and flag things that no longer
>> parse? (I don't even know if this is something reasonable to attempt.)
>>
>> My fear is just we've already got a lot of "broken" (without defining that)
>> layers in the index, and I think it will be worse once the python3 change
>> happens. I'd really like to make sure we don't confuse people with various
>> errors.
>>
>
> As it is a hard cut anyway, call it YP 3.0 (!) and start with an empty
> layerindex for 3.0 and only add layers that parse or are maintained.
> Legacy is 1.x/2.x and will be a separate page.
That would be the lest disruptive but I fear the Python3 switch over
wont happen for a very long time. The same people doing that work would
most likely be active on or maintaining 2.x
- armin
>
>
> --
> Jan-Simon Möller
> dl9pf@gmx.de
>
next prev parent reply other threads:[~2016-05-05 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 8:56 Python 3 for Bitbake Richard Purdie
2016-05-04 21:19 ` Christopher Larson
2016-05-04 21:29 ` [Openembedded-architecture] " Mark Hatle
2016-05-04 21:34 ` Burton, Ross
2016-05-05 5:10 ` Tim Orling
2016-05-06 8:40 ` Burton, Ross
2016-05-05 12:13 ` Philip Balister
2016-05-05 15:13 ` Mark Hatle
2016-05-05 15:18 ` Christopher Larson
2016-05-05 15:50 ` Otavio Salvador
2016-05-05 17:29 ` Jan-Simon Möller
2016-05-05 17:47 ` Otavio Salvador
2016-05-05 17:50 ` akuster [this message]
2016-05-09 20:39 ` Richard Purdie
2016-05-22 7:58 ` 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=572B87E3.9020105@mvista.com \
--to=akuster@mvista.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=dl9pf@gmx.de \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=philip@balister.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