From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH] migration-guides: prepare for release 3.5
Date: Fri, 17 Dec 2021 15:04:15 +0100 [thread overview]
Message-ID: <20211217140415.49840-1-michael.opdenacker@bootlin.com> (raw)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/migration-guides/index.rst | 1 +
.../migration-guides/migration-3.5.rst | 37 +++++++++++++++++++
2 files changed, 38 insertions(+)
create mode 100644 documentation/migration-guides/migration-3.5.rst
diff --git a/documentation/migration-guides/index.rst b/documentation/migration-guides/index.rst
index 287b553195..6472cc2848 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.5
migration-3.4
migration-3.3
migration-3.2
diff --git a/documentation/migration-guides/migration-3.5.rst b/documentation/migration-guides/migration-3.5.rst
new file mode 100644
index 0000000000..c63c9dff05
--- /dev/null
+++ b/documentation/migration-guides/migration-3.5.rst
@@ -0,0 +1,37 @@
+Release 3.5 (kirkstone)
+=======================
+
+This section provides migration information for moving to the Yocto
+Project 3.5 Release (codename "kirkstone") from the prior release.
+
+Recipe changes
+--------------
+
+- Because of the uncertainty in future default branch names in git repositories,
+ it is now required to add a branch name to all URLs described
+ by ``git://`` and ``gitsm://`` :term:`SRC_URI` entries. For example::
+
+ SRC_URI = "git://git.denx.de/u-boot.git;branch=master"
+
+ A :oe_git:`convert-srcuri </openembedded-core/tree/scripts/contrib/convert-srcuri.py>`
+ script to convert your recipes is available in :term:`OpenEmbedded-Core (OE-Core)`
+ and in :term:`Poky`.
+
+- Because of `GitHub dropping support for the git:
+ protocol <https://github.blog/2021-09-01-improving-git-protocol-security-github/>`,
+ recipes now need to use ``;protocol=https`` at the end of GitHub
+ URLs. The same script as above can be used to convert the recipes.
+
+- The :term:`TOPDIR` variable and the current working directory are no longer modified
+ when parsing recipes. Any code depending on that behaviour will no longer worked as
+ expected (we don't know of any).
+
+- BitBake no longer supports ``append``, ``prepend`` and ``remove`` operators
+ combined with the ``+=``, ``=+``, ``.=``, ``=.`` and ``?=`` operators.
+ Such operations should be made using ``=`` alone. This means that
+ a leading space may need to be explicitly added.
+
+- :ref:`allarch <ref-classes-allarch>` packagegroups can no longer depend on packages
+ which use ``PKG:xxx`` renaming such as :ref:`debian.bbclass <ref-classes-debian>`.
+ Doing this will produce an error.
+
--
2.25.1
next reply other threads:[~2021-12-17 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 14:04 Michael Opdenacker [this message]
2021-12-21 23:58 ` [docs] [PATCH] migration-guides: prepare for release 3.5 Peter Kjellerstedt
2022-01-03 10:32 ` Quentin Schulz
2022-01-17 12:51 ` Richard Purdie
2022-01-17 12:56 ` Alexander Kanavin
2022-01-18 13:07 ` [PATCH] migration-3.5: mention task specific network access Michael Opdenacker
2022-01-18 13:41 ` [docs] " 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=20211217140415.49840-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.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.