OEDAM 2017
Contents
- 1 Location and Time
- 2 Attendees
- 3 Agenda Items
- 3.1 Berlin AR's
- 3.1.1 LTS
- 3.1.2 Windriver ‘setup’ Demo
- 3.1.3 Devtool and other stuff (10:04)
- 3.1.4 Suggestion for improvement of how to handle site and user configuration.
- 3.1.5 BSPs and layer name recommendations
- 3.1.6 OTA
- 3.1.7 Layer Quality
- 3.1.8 Make perl and python distro features? [Saur]
- 3.1.9 Support for meson build system? [Saur]
- 3.1.10 The use of ${COREBASE}/LICENSE in LIC_FILES_CHKSUM. [Saur]
- 3.1.11 Discuss merging duplicate classes and recipes (metadata)
- 3.1.12 Changes to deploy_image
- 3.1.13 Discussion on mesa and splitting libgbm
- 3.1.14 Discussion of recipe maintainers for oe-core and beyond
- 3.1 Berlin AR's
- 4 Minutes
Location and Time
Monday February 20 2017
Location:
Mentor Graphics
8005 Boeckman Rd
Wilsonville, OR 97070
Phone: (800) 547-3000
9am-5pm
(Before ELC [Feb 21-23] and Yocto Project Developer Day [Feb 24])
Attendees
- Armin Kuster (armpit)
- Philip Balister (Crofton)
- Trevor Woerner (tlwoerner)
- Denys Dmytriyenko (denix)
- Stephano Cetola
- Matthew McClintock
- Tim Orling (moto-timo)
- James Perkins (jamesp)
- Patrick Ohly (pohly)
- Richard Purdie (RP)
- Mark Hatle (fray)
- Jan-Simon Möller (dl9pf)
- Derek Straka
- Scott Murray (scottm)
Agenda Items
- Review items from last meeting in Berlin (Please add remarks)
- Proposal (Patrick): stateless distro
- Proposal (Patrick): GPLv3 handling - remove recipes for obsolete components, replace with adaptive recipe and image configurations (like disabling readline support)
- Proposal (Patrick): remove openembedded-devel@lists.openembedded.org Reply-To?
Berlin AR's
LTS
Yocto-Compatibility requires pushing patches upstream, but Yocto doesn't handle QA for old releases A lot of work for the software vendors rp: have new/separate LTS tree for older releases crofton: how to coordinate between ppl who want this, collect interest in the wiki add maintainer information to the layer repos? rp: write a proposal? → enough interest to set this up
action: Armin will start conversation on the Architecture list Not completed
Windriver ‘setup’ Demo
Conclusion: We want it in OE instead of Yocto (unanimous) Mark: Once able to contribute, talk to halstead for new repo. Repo published. OE has not taken over
Notes: Layer Index was recently updated and this was required before progress can be made on promoting this tool.
I would like to talk about the next steps at the OEDAM, now that everything is public.
Devtool and other stuff (10:04)
Sysroot-Contamination rp: solution “sysroot per recipe”
Suggestion for improvement of how to handle site and user configuration.
Conclusion: Saur will implement the BBPATH_EXTRA and discuss it on the list.
BSPs and layer name recommendations
RP: We can do this by … For Compatible v2 we want to raise the bar. Sanity check for things that keep breaking. Conclusion: Jan-Simon will start a script check the basic stuff, RP should add the checksum checks.
OTA
RP: This discussion needs to continue beyond OEDEM
Layer Quality
Conclusion: We need to get the word out and get suggestions.
Make perl and python distro features? [Saur]
Conclusion: No change.
Support for meson build system? [Saur]
Conclusion: Patches welcome, talk to Ross.
The use of ${COREBASE}/LICENSE in LIC_FILES_CHKSUM. [Saur]
Conclusion: RP: This needs to go to the ML
Discuss merging duplicate classes and recipes (metadata)
Conclusion: Duplicate recipes and machines need to be brought up with the maintainers.
Conclusion: Mark, RP, Chris and others should look to create a proposal about resolving the confusion over layer order/priority/etc.
Changes to deploy_image
Conclusion: Document
Discussion on mesa and splitting libgbm
Conclusion: RP: Topic should be discussed with Ross on mailing list.
Discussion of recipe maintainers for oe-core and beyond
RP: This list is a Yocto initiative. They try to get more involvement from the members. There is an incentive to get more ppl involved (recipe reporting system):