[yocto] 2.6 migration guide

[Paul Eggleton]

Hi folks

When Scott prepares the migration guide for a release, he usually looks to me
to collate the notable changes for it (those requiring user intervention). I
haven't prepared anything yet though and the 2.6 release is fast approaching.
Can anyone who has been involved in or is aware of such changes in master for
upcoming 2.6 (thud) make a note of it on the wiki in raw form on this page:

https://wiki.yoctoproject.org/wiki/FutureMigrationGuide

Scott and I will take care of cleaning it up, so things added there don't need
to be perfect.

I will also be doing my usual trawl through the commits in the release for the
more general changelog, so most things will get picked up that way, but it's
really helpful if people with first-hand knowledge of the implications of some
of these changes are involved in how they get documented.

Thanks,
Paul

[Scott Rifenbark]

Paul,

Thanks for sending.

Contributors....

I have an initial section at
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
which is based on Richard's input. I am sure there are more items.

Thanks,
Scott

Post by Paul Eggleton
Hi folks
When Scott prepares the migration guide for a release, he usually looks to me
to collate the notable changes for it (those requiring user intervention). I
haven't prepared anything yet though and the 2.6 release is fast approaching.
Can anyone who has been involved in or is aware of such changes in master for
https://wiki.yoctoproject.org/wiki/FutureMigrationGuide
Scott and I will take care of cleaning it up, so things added there don't need
to be perfect.
I will also be doing my usual trawl through the commits in the release for the
more general changelog, so most things will get picked up that way, but it's
really helpful if people with first-hand knowledge of the implications of some
of these changes are involved in how they get documented.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre

[Scott Rifenbark]

Thanks Robert... I will do that.

Scott

On Wed, Oct 31, 2018 at 12:15 AM Robert Berger <

Hi Scott,

Post by Scott Rifenbark
I have an initial section at

https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,

Post by Scott Rifenbark
which is based on Richard's input. I am sure there are more items.

You might want to add a link to the bitbake manual or some example from
http://git.openembedded.org/bitbake/tree/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml?id=c0a23dd9155c50a6b7df796980bc7b612cac7994#n334
FOO = "123 456 789 123456 123 456 123 456"
FOO_remove = "123"
FOO_remove = "456"
FOO is now: " 789 123456 " instead of "789 123456"

Post by Scott Rifenbark
Thanks,
Scott

Regards,
Robert

[Scott Rifenbark]

Can you tell me why "123456" is also not removed? That string contains
instances of "123" and "456"

Thanks,
Scott

On Wed, Oct 31, 2018 at 12:15 AM Robert Berger <

Hi Scott,

Post by Scott Rifenbark
I have an initial section at

https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,

Post by Scott Rifenbark
which is based on Richard's input. I am sure there are more items.

You might want to add a link to the bitbake manual or some example from
http://git.openembedded.org/bitbake/tree/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml?id=c0a23dd9155c50a6b7df796980bc7b612cac7994#n334
FOO = "123 456 789 123456 123 456 123 456"
FOO_remove = "123"
FOO_remove = "456"
FOO is now: " 789 123456 " instead of "789 123456"

Post by Scott Rifenbark
Thanks,
Scott

Regards,
Robert

[Bas Mevissen]

Post by Scott Rifenbark
Can you tell me why "123456" is also not removed? That string contains
instances of "123" and "456"

Because it removes all occurrences of the list value "123" and not of
value "123456" or any part of it. Otherwise, it would be impossible to
use this function to only remove, say, "1" from a long list of numbers.
(here 'value' is not limited to a number).

-- Bas.

Post by Scott Rifenbark
Thanks,
Scott
On Wed, Oct 31, 2018 at 12:15 AM Robert Berger

Hi Scott,

Post by Scott Rifenbark
I have an initial section at
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
which is based on Richard's input. I am sure there are more items.

You might want to add a link to the bitbake manual or some example from
http://git.openembedded.org/bitbake/tree/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml?id=c0a23dd9155c50a6b7df796980bc7b612cac7994#n334
FOO = "123 456 789 123456 123 456 123 456"
FOO_remove = "123"
FOO_remove = "456"
FOO is now: " 789 123456 " instead of "789 123456"

Post by Scott Rifenbark
Thanks,
Scott

Regards,
Robert

--

[Scott Rifenbark]

Got it, thanks.

Post by Bas Mevissen

Post by Scott Rifenbark
Can you tell me why "123456" is also not removed? That string contains
instances of "123" and "456"

Because it removes all occurrences of the list value "123" and not of
value "123456" or any part of it. Otherwise, it would be impossible to
use this function to only remove, say, "1" from a long list of numbers.
(here 'value' is not limited to a number).
-- Bas.

Post by Scott Rifenbark
Thanks,
Scott
On Wed, Oct 31, 2018 at 12:15 AM Robert Berger

Hi Scott,

Post by Scott Rifenbark
I have an initial section at

https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release
,

Post by Scott Rifenbark

Post by Scott Rifenbark
which is based on Richard's input. I am sure there are more items.

You might want to add a link to the bitbake manual or some example from

http://git.openembedded.org/bitbake/tree/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml?id=c0a23dd9155c50a6b7df796980bc7b612cac7994#n334

Post by Scott Rifenbark

FOO = "123 456 789 123456 123 456 123 456"
FOO_remove = "123"
FOO_remove = "456"
FOO is now: " 789 123456 " instead of "789 123456"

Post by Scott Rifenbark
Thanks,
Scott

Regards,
Robert

[Peter Kjellerstedt]

In “4.14.2. OpenSSL Changes”, change “both versions their dependency chains” to “both versions in their dependency chains”.
In “4.14.4. Security Changes”, change “files” to “flags” (twice).

//Peter

From: openembedded-core-***@lists.openembedded.org <openembedded-core-***@lists.openembedded.org> On Behalf Of Scott Rifenbark
Sent: den 30 oktober 2018 23:07
To: Paul Eggleton <***@linux.intel.com>
Cc: Yocto discussion list <***@yoctoproject.org>; openembedded-core <openembedded-***@lists.openembedded.org>
Subject: Re: [OE-core] 2.6 migration guide

Paul,

Thanks for sending.

Contributors....

I have an initial section at https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release, which is based on Richard's input. I am sure there are more items.

Thanks,
Scott

On Tue, Oct 23, 2018 at 2:14 PM Paul Eggleton <***@linux.intel.com<mailto:***@linux.intel.com>> wrote:
Hi folks

When Scott prepares the migration guide for a release, he usually looks to me
to collate the notable changes for it (those requiring user intervention). I
haven't prepared anything yet though and the 2.6 release is fast approaching.
Can anyone who has been involved in or is aware of such changes in master for
upcoming 2.6 (thud) make a note of it on the wiki in raw form on this page:

https://wiki.yoctoproject.org/wiki/FutureMigrationGuide

Scott and I will take care of cleaning it up, so things added there don't need
to be perfect.

I will also be doing my usual trawl through the commits in the release for the
more general changelog, so most things will get picked up that way, but it's
really helpful if people with first-hand knowledge of the implications of some
of these changes are involved in how they get documented.

Thanks,
Paul

[Scott Rifenbark]

Peter,

Thanks
Scott

https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#migration-2.6-openssl-changes
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#migration-2.6-security-changes

On Fri, Nov 2, 2018 at 8:10 AM Peter Kjellerstedt <

Post by Peter Kjellerstedt
In “4.14.2. OpenSSL Changes”, change “both versions their dependency
chains” to “both versions in their dependency chains”.
In “4.14.4. Security Changes”, change “files” to “flags” (twice).
//Peter
Rifenbark
*Sent:* den 30 oktober 2018 23:07
*Subject:* Re: [OE-core] 2.6 migration guide
Paul,
Thanks for sending.
Contributors....
I have an initial section at
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
which is based on Richard's input. I am sure there are more items.
Thanks,
Scott
On Tue, Oct 23, 2018 at 2:14 PM Paul Eggleton <
Hi folks
When Scott prepares the migration guide for a release, he usually looks to me
to collate the notable changes for it (those requiring user intervention). I
haven't prepared anything yet though and the 2.6 release is fast approaching.
Can anyone who has been involved in or is aware of such changes in master for
https://wiki.yoctoproject.org/wiki/FutureMigrationGuide
Scott and I will take care of cleaning it up, so things added there don't need
to be perfect.
I will also be doing my usual trawl through the commits in the release for the
more general changelog, so most things will get picked up that way, but it's
really helpful if people with first-hand knowledge of the implications of some
of these changes are involved in how they get documented.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre

[Paul Eggleton]

Post by Scott Rifenbark
I have an initial section at
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
which is based on Richard's input. I am sure there are more items.

OK, so I have removed Richard's items from the wiki page (since they're now
in the manual) and added items I have gathered from reviewing all of the
git commits in the release. Let me know if you need clarification on anything
- everyone else, let us know if I missed or messed up something.

https://wiki.yoctoproject.org/wiki/FutureMigrationGuide

BTW I think the section on postinstalls (from Richard's input) is a little terse
and needs expansion - most importantly it needs to describe what actions the
user might need to take. I'll take care of this on review if nobody else does.

Cheers,
Paul

[Paul Eggleton]

Post by Paul Eggleton

Post by Scott Rifenbark
I have an initial section at
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
which is based on Richard's input. I am sure there are more items.

OK, so I have removed Richard's items from the wiki page (since they're now
in the manual) and added items I have gathered from reviewing all of the
git commits in the release. Let me know if you need clarification on anything
- everyone else, let us know if I missed or messed up something.
https://wiki.yoctoproject.org/wiki/FutureMigrationGuide

I forgot one thing:

------- snip -------

Python 3 profile-guided optimisation
-----------------------------------------------

The python3 recipe now enables profile-guided optimisation; this requires a little extra build time in exchange for improved performance on the target at runtime, and is only enabled if the current MACHINE has support for user-mode emulation in QEMU (i.e. "qemu-usermode" is in MACHINE_FEATURES, which it is by default, so the machine configuration would need to have opted out for it not to be). If you wish to disable Python profile-guided optimisation regardless of the value of MACHINE_FEATURES, then ensure that PACKAGECONFIG for python3 does not contain "pgo". You could accomplish the latter using PACKAGECONFIG_pn-python3 = "pgo" at the configuration level or by setting PACKAGECONFIG using a bbappend for the python3 recipe.

------- snip -------

Post by Paul Eggleton
BTW I think the section on postinstalls (from Richard's input) is a little terse
and needs expansion - most importantly it needs to describe what actions the
user might need to take. I'll take care of this on review if nobody else does.

So what I think we need here is to copy part of the "Using exit 1 to explicitly defer a postinstall script until first boot..." paragraph that's mentioned in the 2.5 migration section. Would it make sense to actually break this out to its own place in the documentation (on "Deferring postinstalls to first boot") and then link to that from both places?

While I think of it, could you also move the _remove item that's in the "Bitbake Changes" section into the "Override Changes" section?

Thanks,
Paul

[Paul Eggleton]

Post by Paul Eggleton
You could accomplish the latter using PACKAGECONFIG_pn-python3 = "pgo" at
the configuration level

Oops, I meant PACKAGECONFIG_remove_pn-python3 = "pgo" here.

Cheers,
Paul