All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Larson <clarson@kergoth.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Philip Balister <philip@balister.org>,
	bitbake-devel <bitbake-devel@lists.openembedded.org>,
	openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Python 3 for Bitbake
Date: Thu, 5 May 2016 08:18:54 -0700	[thread overview]
Message-ID: <CABcZANkm4caMHo2kutQFBfzhVNxyD50xSS7K0vnHSpmKJj6qvQ@mail.gmail.com> (raw)
In-Reply-To: <fce22d23-e66c-c692-f7d5-f1154081246a@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]

On Thu, May 5, 2016 at 8:13 AM, Mark Hatle <mark.hatle@windriver.com> wrote:

> On 5/5/16 7:13 AM, Philip Balister wrote:
> > On 05/04/2016 05:29 PM, Mark Hatle wrote:
> >> On 5/4/16 3:56 AM, Richard Purdie wrote:
> >>> My proposal is we decide to have the flag day, we queue up the patches
> >>> on a python3 branch both in oe-core and bitbake, then we switch when we
> >>> get successful autobuilder builds. I'd ideally like to do this quite
> >>> soon and get one with it (within a few weeks), leaving plenty of time
> >>> to handle issues and the other changes planned for this release cycle
> >>> and give other layers time to adapt.
> >>>
> >>> I will likely push things so the basics in the core work, I'll then
> >>> need help for things like toaster, the QA framework, the supporting
> >>> tools (devtool, recipetool and so on).
> >>>
> >>> Does anyone object to this?
> >>
> >> I think this is a good plan.  Flag day, and switch.
> >>
> >> 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.


Perhaps we should consider some sort of flag or dependency/versioning
statement in layer.conf?
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 2723 bytes --]

  reply	other threads:[~2016-05-05 15:19 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 [this message]
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
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=CABcZANkm4caMHo2kutQFBfzhVNxyD50xSS7K0vnHSpmKJj6qvQ@mail.gmail.com \
    --to=clarson@kergoth.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mark.hatle@windriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.