From: Philip Balister <philip@balister.org>
To: Rudolf J Streif <rudolf.streif@gmail.com>, yocto@yoctoproject.org
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Yocto Project Status WW09
Date: Fri, 26 Feb 2016 15:16:24 -0500 [thread overview]
Message-ID: <56D0B298.9050108@balister.org> (raw)
In-Reply-To: <2042150.gN3rpHrprf@rjs-zotac.streifs.net>
On 02/26/2016 02:52 PM, Rudolf J Streif wrote:
>>>>
>>>> * We're about to try and transition meta-yocto within meta-yocto to
>>>>
>>>> meta-poky. The amount of pain this is causing is horrible :(.
>>>
>>> Thanks for doing this. Can you summarize the pain? Are there any
>>> important lessons here?
>>
>> The key lesson is our current "migration" code in OE-Core sucks and I
>> have some patches in progress which rewrite pieces of it in a way that
>> makes it more useful. I'm therefore trying to make some positives from
>> it.
>>
>> That said, I haven't found a way to make this work without leaving a
>> dummy layer.conf in the old location since a missing layer.conf file is
>> fatal to bitbake very early on before any migration code triggers.
>>
>> More should become clear when I post the patches, I've been holding off
>> that until I actually manage a patch set that works on the
>> autobuilder...
>>
>> Patches should be out over the weekend (in time for the freeze).
>
> Sounds like a lot of work and potential for breaking things with little added
> value other than a more consistent naming. What was the rationale for making
> the change, if I may ask?
Consistent naming :) It does it make it much easier to explain what the
meta-yocto layer is for. This has been one source of a great deal of
confusion about how all the pieces come together.
I must admit, I'm surprised this is tricky. I look forward to seeing
what needs doing. Hopefully, it shows me things I can avoid in my work.
Philip
>
> Thanks,
> :rjs
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Philip Balister <philip@balister.org>
To: Rudolf J Streif <rudolf.streif@gmail.com>, yocto@yoctoproject.org
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Yocto Project Status WW09
Date: Fri, 26 Feb 2016 15:16:24 -0500 [thread overview]
Message-ID: <56D0B298.9050108@balister.org> (raw)
In-Reply-To: <2042150.gN3rpHrprf@rjs-zotac.streifs.net>
On 02/26/2016 02:52 PM, Rudolf J Streif wrote:
>>>>
>>>> * We're about to try and transition meta-yocto within meta-yocto to
>>>>
>>>> meta-poky. The amount of pain this is causing is horrible :(.
>>>
>>> Thanks for doing this. Can you summarize the pain? Are there any
>>> important lessons here?
>>
>> The key lesson is our current "migration" code in OE-Core sucks and I
>> have some patches in progress which rewrite pieces of it in a way that
>> makes it more useful. I'm therefore trying to make some positives from
>> it.
>>
>> That said, I haven't found a way to make this work without leaving a
>> dummy layer.conf in the old location since a missing layer.conf file is
>> fatal to bitbake very early on before any migration code triggers.
>>
>> More should become clear when I post the patches, I've been holding off
>> that until I actually manage a patch set that works on the
>> autobuilder...
>>
>> Patches should be out over the weekend (in time for the freeze).
>
> Sounds like a lot of work and potential for breaking things with little added
> value other than a more consistent naming. What was the rationale for making
> the change, if I may ask?
Consistent naming :) It does it make it much easier to explain what the
meta-yocto layer is for. This has been one source of a great deal of
confusion about how all the pieces come together.
I must admit, I'm surprised this is tricky. I look forward to seeing
what needs doing. Hopefully, it shows me things I can avoid in my work.
Philip
>
> Thanks,
> :rjs
>
>
next prev parent reply other threads:[~2016-02-26 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 17:36 Yocto Project Status WW09 Richard Purdie
2016-02-26 17:36 ` [OE-core] " Richard Purdie
2016-02-26 18:45 ` Philip Balister
2016-02-26 18:45 ` [OE-core] " Philip Balister
2016-02-26 18:50 ` Richard Purdie
2016-02-26 18:50 ` [OE-core] " Richard Purdie
2016-02-26 19:52 ` [yocto] " Rudolf J Streif
2016-02-26 19:52 ` [OE-core] " Rudolf J Streif
2016-02-26 20:16 ` Philip Balister [this message]
2016-02-26 20:16 ` Philip Balister
2016-02-26 20:58 ` [yocto] " Burton, Ross
2016-02-26 20:58 ` [OE-core] " Burton, Ross
2016-02-27 1:29 ` [yocto] " Christopher Larson
2016-02-27 1:29 ` [OE-core] " Christopher Larson
2016-02-29 11:10 ` FW: " Barros Pena, Belen
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=56D0B298.9050108@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rudolf.streif@gmail.com \
--cc=yocto@yoctoproject.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.