DOs and DON'Ts when building a Yocto based distribution
What we have learned in a year of building Oniro
- Track: Distributions devroom
- Room: D.distributions
- Day: Sunday
- Start: 15:45
- End: 16:10
- Video with Q&A: D.distributions
- Video only: D.distributions
- Chat: Join the conversation!
After approximately a year of work, Oniro - the Eclipse Foundation's embedded operating system - has been released to the public, and is open to bigger changes like rebasing to a newer Yocto branch and updating toolchains. Now we're seeing - and can share - what we did well and what we will have to do differently in the future.
After approximately a year of work, Oniro (https://oniroproject.org/) - the Eclipse Foundation's embedded operating system - has been released to the public, and is open to bigger changes like rebasing to a newer Yocto branch and updating toolchains. Now we're seeing - and can share - what we did well and what we will have to do differently in the future.
We updated a number of packages from dunfell - can this be avoided or done in a better way? What can we do about packages that don't have an LTS policy?
An important goal must be to make rebasing to newer upstream releases as quick and painless as possible - accumulating as little technical debt as we can.
Speakers
 |
Bernhard Rosenkränzer |
 |
Andrei Gherzan |