From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Maik Vermeulen <maik.vermeulen@lightyear.one>,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] Upgrading from sumo to more recent version
Date: Tue, 29 Nov 2022 13:00:34 +0000 [thread overview]
Message-ID: <2bcc5965138170e205fd605fb0bc8e76b5236185.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAKO9uzrfjAtjAL15pTb6F52UL5=OT1crYG_7bdBDU6kkwKNs-A@mail.gmail.com>
On Tue, 2022-11-29 at 13:51 +0100, Maik Vermeulen wrote:
> After some questions on this mailing list, we got comments on our
> usage of quite an old yocto poky version: sumo.
>
> What are the steps to upgrade to a newer version?
> We have quite some of our own recipes, and also some
> proprietary third party patches.
>
> Do we go version by version from sumo to the most recent one, or big
> bang?
> Are there tools to for example fix and replace the old notation by
> the new one?
> Any other tips?
There is extensive documentation about moving between releases here
with our migration guides between each version:
https://docs.yoctoproject.org/migration-guides/index.html
That will include information about the migration tools where
available.
Personally, I'd probably try working with the last release or last LTS
and then try and get everything you need working with that rather than
doing it incrementally but a lot depends on your experience/needs and
the kinds of changes you have.
Cheers,
Richard
next prev parent reply other threads:[~2022-11-29 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 12:51 Upgrading from sumo to more recent version Maik Vermeulen
2022-11-29 13:00 ` Richard Purdie [this message]
2022-11-29 15:52 ` [yocto] " Philip Balister
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=2bcc5965138170e205fd605fb0bc8e76b5236185.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=maik.vermeulen@lightyear.one \
--cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox