| Summary: | Merge machine specific config recipes into one recipe to rule them all | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Richard Purdie <richard.purdie> |
| Component: | core | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | akuster, alexandru.c.georgescu, dvhart, jose.perez.carranza, mark.hatle, meta.mr.watcher, meta.watcher, randy.macleod, ross.burton, srifenbark |
| Version: | 5.99 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| See Also: | http://bugzilla.yoctoproject.org/show_bug.cgi?id=6362 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Richard Purdie
2013-03-11 21:12:31 UTC
Here is the list of recipes that contain config files for qemu currently meta/recipes-bsp/pointercal meta/recipes-bsp/formfactor meta/recipes-core/init-ifupdown/init-ifupdown-1.0 meta/recipes-connectivity/connman/connman-conf meta/recipes-graphics/xorg-xserver/xserver-xf86-config Darren's bug 6362 also points out alsa-state is another one. Some others that might fall into this category are: tslib.conf (still used by directfb and qt4-embedded), maybe we need to bluez's bluetooth.com apmd_proxy.conf Anything I missed? keymaps, alsa-state, pointercal, pointercal-xinput, come to mind My proposal is to move all the BSP related config files into one recipe directory tree. Create a recipe that can have a package or packages that are RRECOMMENDS on.
We have 2 choices on the packaging side:
1) 1 Package to rule them all (conffiles)
- RPROVIDES PN-conf
- conffile.bbclass
RRECOMMENDS = "${PN}-conf"
# Can be overriden in recipe
CONFFILES_conffiles ?= "${PN}.conf"
- Will provide files not needed on final image, small
amount of extra space used.
2) 1 package / conf file (${PN}-conf)
- exactly what's needed will be installed
- no needs for additional RPROVIDES
- More packaging overhead, package data might be bigger than actual contents!
I am unsure how either of the solutions in Comment 3 exactly would affect the user documentation. Solution 1 looks like a new class would be added (i.e. conffile.bbclass). Would there be a shift in how the user goes about providing configuration files? This is what I am missing. When a solution for this bug is figured out I will need more explanation for the doc updates. Thanks, Scott NOTE: Here are a couple spots of interest that might be affected? Not sure but I am noting them here: * The "Configuration Files" item in the http://www.yoctoproject.org/docs/1.9/dev-manual/dev-manual.html#yocto-project-terms section. * The Note in Step 4 of the http://www.yoctoproject.org/docs/1.9/dev-manual/dev-manual.html#developing-a-board-support-package-bsp section. is this still an issue? Is still a valid issue. |