From: "Quentin Schulz" <quentin.schulz@theobroma-systems.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: docs@lists.yoctoproject.org,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Quentin Schulz <foss@0leil.net>
Subject: Re: [docs] [PATCH v2] migration-guides: Add start of 3.4 guide with override migration notes
Date: Fri, 30 Jul 2021 12:33:04 +0200 [thread overview]
Message-ID: <20210730103304.fb5d2b4aqfwszt4z@fedora> (raw)
In-Reply-To: <20210730094757.177431-1-michael.opdenacker@bootlin.com>
Hi Michael,
On Fri, Jul 30, 2021 at 11:47:57AM +0200, Michael Opdenacker wrote:
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> Reviewed-by: Quentin Schulz <foss@0leil.net>
Please don't add my Reviewed-by if I haven't given it :)
> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> ---
> documentation/migration-guides/index.rst | 1 +
> .../migration-guides/migration-3.4.rst | 74 +++++++++++++++++++
> 2 files changed, 75 insertions(+)
> create mode 100644 documentation/migration-guides/migration-3.4.rst
>
> diff --git a/documentation/migration-guides/index.rst b/documentation/migration-guides/index.rst
> index 6304e6318c..287b553195 100644
> --- a/documentation/migration-guides/index.rst
> +++ b/documentation/migration-guides/index.rst
> @@ -12,6 +12,7 @@ to move to one release of the Yocto Project from the previous one.
> .. toctree::
>
> migration-general
> + migration-3.4
> migration-3.3
> migration-3.2
> migration-3.1
> diff --git a/documentation/migration-guides/migration-3.4.rst b/documentation/migration-guides/migration-3.4.rst
> new file mode 100644
> index 0000000000..4aa5271724
> --- /dev/null
> +++ b/documentation/migration-guides/migration-3.4.rst
> @@ -0,0 +1,74 @@
> +Release 3.4 (honister)
> +======================
> +
> +This section provides migration information for moving to the Yocto
> +Project 3.4 Release (codename "honister") from the prior release.
> +
> +Override syntax changes
> +-----------------------
> +
> +This release requires changes to the metadata to indicate where overrides are
> +being used in variable key names. This is done with the ``:`` character replacing
> +the use of ``_`` previously. This means that an entry like::
> +
> + SRC_URI_qemux86 = "file://somefile"
> +
> +becomes::
> +
> + SRC_URI:qemux86 = "file://somefile"
> +
> +since ``qemux86`` is an override. This applies to any use of override syntax so::
> +
> + SRC_URI_append = " file://somefile"
> + SRC_URI_append_qemux86 = " file://somefile2"
> + SRC_URI_remove_qemux86-64 = " file://somefile3"
> + SRC_URI_prepend_qemuarm = "file://somefile4 "
> + FILES_${PN}-ptest = "${bindir}/xyz"
> + IMAGE_CMD_tar = "tar"
> + BASE_LIB_tune-cortexa76 = "lib"
> + SRCREV_pn-bash = "abc"
> + BB_TASK_NICE_LEVEL_task-testimage = '0'
> +
> +becomes::
> +
> + SRC_URI:append = " file://somefile"
> + SRC_URI:append:qemux86 = " file://somefile2"
> + SRC_URI:remove:qemux86-64 = " file://somefile3"
> + SRC_URI:prepend:qemuarm = "file://somefile4 "
> + FILES:${PN}-ptest = "${bindir}/xyz"
> + IMAGE_CMD:tar = "tar"
> + BASE_LIB:tune-cortexa76 = "lib"
> + SRCREV:pn-bash = "abc"
> + BB_TASK_NICE_LEVEL:task-testimage = '0'
> +
> +This also applies to variable queries to the datastore, for example using getVar
getVar to be tick quoted?
Maybe we can link to:
https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html?functions-for-accessing-datastore-variables
for the various queries to the datastore?
Reviewed-by: Quentin Schulz <foss@0leil.net>
Thanks!
> +and similar so ``d.getVar("RDEPENDS_${PN}")`` becomes ``d.getVar("RDEPENDS:${PN}")``.
> +
Just something that popped up in my mind but we should be careful when
updating the docs to use : instead of _ since I seem to recall that we
have some ``RDEPENDS_*`` or similar that we could actually replace by
:term:`RDEPENDS` now :)
I've yet to read the udpated documentation (if there's something
available somewhere already?) and check a bit what's handled by the
script done by Richard :)
Cheers,
Quentin
next prev parent reply other threads:[~2021-07-30 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16968778436D0C00.13113@lists.yoctoproject.org>
2021-07-30 9:45 ` [PATCH v2] migration-guides: Add start of 3.4 guide with override migration notes Michael Opdenacker
2021-07-30 9:47 ` Michael Opdenacker
2021-07-30 10:33 ` Quentin Schulz [this message]
2021-07-30 14:06 ` [docs] " Michael Opdenacker
[not found] ` <1696886EF6A201F4.6707@lists.yoctoproject.org>
2021-07-30 9:49 ` Michael Opdenacker
[not found] ` <1696889367F9FDB7.13113@lists.yoctoproject.org>
2021-07-30 10:07 ` Michael Opdenacker
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=20210730103304.fb5d2b4aqfwszt4z@fedora \
--to=quentin.schulz@theobroma-systems.com \
--cc=docs@lists.yoctoproject.org \
--cc=foss@0leil.net \
--cc=michael.opdenacker@bootlin.com \
--cc=richard.purdie@linuxfoundation.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