Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: #yocto methodology to port from older yocto revisions to current
Date: Mon, 19 Oct 2020 11:22:41 +0000	[thread overview]
Message-ID: <MADEUP.163F60F774955E72.8803@lists.yoctoproject.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 577 bytes --]


Hello:

I am currently at Yocto release "Rocko 2.4.1" and I am looking into the effort to port to the latest Yocto release...

We have been using this  rocko platform revision for the last few years in a project, and now want to move to the latest supported release.

Is there a preferred established methodology/guidelines when porting projects from much older established revisions of Yocto?

Is it considered better to port an established project directly to a new Yocto release, or to slowly migrate the yocto revision to the desired release ?

Thanks,
Steve

[-- Attachment #2: Type: text/html, Size: 2716 bytes --]

             reply	other threads:[~2020-10-19 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 11:22 Monsees, Steven C (US) [this message]
2020-10-19 11:29 ` [yocto] #yocto methodology to port from older yocto revisions to current Quentin Schulz
2020-10-19 11:49   ` Alexander Kanavin

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=MADEUP.163F60F774955E72.8803@lists.yoctoproject.org \
    --to=steven.monsees@baesystems.com \
    --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