2.6 migration guide

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

--
Paul Eggleton
Intel Open Source Technology Centre

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

Hi Scott,

Quoted 3 lines · 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,

Quoted 1 line

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 there for the new functionality of _remove operator:

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"

Quoted 3 lines

Thanks,
Scott

Regards,

Robert

Hi Scott,

Quoted 3 lines · 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,

Quoted 1 line

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 there for the new functionality of _remove operator:

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"

Quoted 3 lines

Thanks,
Scott

Regards,

Robert

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

Thanks,
Scott

Quoted 26 lines · Robert Berger

Hi Scott,

Quoted 4 lines · 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 there for the new functionality of _remove operator:

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"

Quoted 3 lines

Thanks,
Scott

Regards,

Robert

Quoted 2 lines · 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.

Quoted 13 lines

Thanks,
Scott

Quoted 6 lines · Robert Berger

Hi Scott,

Quoted 3 lines · 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
,

Quoted 7 lines

Quoted 7 lines

Quoted 1 line

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
there for the new functionality of _remove operator:

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

Quoted 14 lines

Quoted 14 lines

FOO = "123 456 789 123456 123 456 123 456"
FOO_remove = "123"
FOO_remove = "456"

FOO is now: " 789 123456 " instead of "789 123456"

Quoted 3 lines

Thanks,
Scott

Regards,

Robert

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:* [email protected] < [email protected]> *On Behalf Of *Scott Rifenbark
*Sent:* den 30 oktober 2018 23:07
*To:* Paul Eggleton <[email protected]>
*Cc:* Yocto discussion list <[email protected]>; openembedded-core < [email protected]>
*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 <
[email protected]> 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

--
Paul Eggleton
Intel Open Source Technology Centre

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.

Quoted 3 lines · NZDT 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.

You could accomplish the latter using PACKAGECONFIG_pn-python3 = "pgo" at the configuration level