Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to Yocto 5.0 (LTS) #97

Open
2 of 10 tasks
KanjiMonster opened this issue Nov 17, 2023 · 3 comments
Open
2 of 10 tasks

Switch to Yocto 5.0 (LTS) #97

KanjiMonster opened this issue Nov 17, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@KanjiMonster
Copy link
Contributor

KanjiMonster commented Nov 17, 2023

Yocto 5.0 (Scarthgap) is planned to be the next LTS release, and is planned for April 24. To keep up to date, we should work on switching to it once it nears the release.

  • Yocto 5.0 released
  • convert templateconf.cfg to a proper configuration template
  • update our recipes/code to work with usrmerge1
  • update meta-open-network-linux to scarthgap
  • update meta-switch to scarthgap
  • update meta-ofdpa to scarthgap
  • update meta-ofdpa-closed to scarthgap
  • decide on the fate of ryu (os-ken)
  • switch to Yocto 5.0
  • verify everything works

1 usrmerge means there is no separate /bin,/lib etc anymore, and everything is now in /usr.

@KanjiMonster KanjiMonster added the enhancement New feature or request label Nov 17, 2023
@KanjiMonster
Copy link
Contributor Author

Yocto 5.0 is out, so we could switch at any time*

@KanjiMonster
Copy link
Contributor Author

Yocto 5.0 will require reorganization of our repository, so let's wait for after 5.2 with this.

@KanjiMonster KanjiMonster added this to the BISDN Linux 6.0 milestone Jul 19, 2024
@KanjiMonster
Copy link
Contributor Author

Most things build with minor changes.

Biggest blocker will be ryu, which uses easy_install from python3's setuptools, which is deprecated and the parts that ryu uses were already removed, so it currently fails to build. Fixing this is a non-trivial change, so we need to discuss if we want to spend the effort, or just drop ryu in 6.0, unless there are customers requiring it.

Os-ken currently has the same issue, so it isn't an alternative, though the likelyhood of it being changed there is higher, as it is actually maintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant