From patchwork Mon Jan 3 17:50:44 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Michael Opdenacker X-Patchwork-Id: 2018 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6AC25C433F5 for ; Mon, 3 Jan 2022 17:50:58 +0000 (UTC) Received: from relay11.mail.gandi.net (relay11.mail.gandi.net [217.70.178.231]) by mx.groups.io with SMTP id smtpd.web08.32021.1641232257331606627 for ; Mon, 03 Jan 2022 09:50:58 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: bootlin.com, ip: 217.70.178.231, mailfrom: michael.opdenacker@bootlin.com) Received: (Authenticated sender: michael.opdenacker@bootlin.com) by relay11.mail.gandi.net (Postfix) with ESMTPSA id 7442F100002; Mon, 3 Jan 2022 17:50:55 +0000 (UTC) From: Michael Opdenacker To: docs@lists.yoctoproject.org Cc: Michael Opdenacker Subject: [PATCH v2] migration-guides: prepare for release 3.5 Date: Mon, 3 Jan 2022 18:50:44 +0100 Message-Id: <20220103175044.36540-1-michael.opdenacker@bootlin.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <16C6D3DEE1986ABF.7129@lists.yoctoproject.org> References: <16C6D3DEE1986ABF.7129@lists.yoctoproject.org> MIME-Version: 1.0 X-GND-Spam-Score: 150 X-GND-Status: SPAM List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Mon, 03 Jan 2022 17:50:58 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/docs/message/2338 Signed-off-by: Michael Opdenacker --- documentation/migration-guides/index.rst | 1 + .../migration-guides/migration-3.5.rst | 44 +++++++++++++++++++ 2 files changed, 45 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..bd807eb8c7 --- /dev/null +++ b/documentation/migration-guides/migration-3.5.rst @@ -0,0 +1,44 @@ +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 ` + 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 `__, + 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 work. + +- The ``append``, ``prepend`` and ``remove`` operators can now only be combined with + ``=`` and ``:=`` operators. To the exception of the ``append`` plus ``+=`` and + ``prepend`` plus ``=+`` combinations, all combinations could be factored up to the + ``append``, ``prepend`` or ``remove`` in the combination. This brought a lot of + confusion on how the override style syntax operators work and should be used. + Therefore, those combinations can simply be replaced by a single ``append``, + ``prepend`` or ``remove`` operator without any additional change. + For the ``append`` plus ``+=`` (and ``prepend`` plus ``=+``) combinations, + the content should be prefixed (respectively suffixed) by a space to maintain + the same behavior. You can learn more about override style syntax operators + (``append``, ``prepend`` and ``remove``) in the BitBake documentation: + :ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:appending and prepending (override style syntax)` + and :ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:removal (override style syntax)`. + +- :ref:`allarch ` packagegroups can no longer depend on packages + which use :term:`PKG` renaming such as :ref:`debian.bbclass `. +