<div dir="ltr"><div>Package management overhead seems like a small-ish price for being able to manage/coordinate custom configs with real depends. Did I mention I like 2) better?<br><br></div>Steve<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, May 27, 2014 at 11:35 AM, Saul Wold <span dir="ltr"><<a href="mailto:sgw@linux.intel.com" target="_blank">sgw@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Folks,<br>
<br>
We have had an open enhancement in the form of bugzilla #4011 (<a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=4011" target="_blank">https://bugzilla.<u></u>yoctoproject.org/show_bug.cgi?<u></u>id=4011</a>).<br>
<br>
I am currently working on this and want to get some feedback regarding the design, the below list of config files would move to one recipe in recipes-bsp, which will reduce the number of .bbappends that a BSP writer might need to create in order to customize the configuration of the BSP.<br>
<br>
Overall, 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.<br>
<br>
We have 2 choices on the packaging side:<br>
<br>
1) 1 Package to rule them all (conffiles)<br>
- RPROVIDES PN-conf<br>
- conffile.bbclass<br>
RRECOMMENDS = "${PN}-conf"<br>
# Can be overriden in recipe<br>
CONFFILES_conffiles ?= "${PN}.conf"<br>
- Will provide files not needed on final image, small<br>
amount of extra space used.<br>
<br>
2) 1 package / conf file (${PN}-conf)<br>
- exactly what's needed will be installed<br>
- no needs for additional RPROVIDES<br>
- More packaging overhead, package data might be bigger than actual contents!<br>
<br>
Currently the list of recipes/config files affected include:<br>
<br>
<br>
meta/recipes-bsp/pointercal/<u></u>pointercal/*/pointercal<br>
meta/recipes-bsp/formfactor/<u></u>files/*/machconfig<br>
meta/recipes-bsp/alsa-state/<u></u>alsa-state/asound.conf<br>
meta/recipes-graphics/xorg-<u></u>xserver/xserver-xf86-config/*/<u></u>xorg.conf<br>
meta/recipes-bsp/keymaps/<u></u>files/keymap.sh<br>
meta/recipes-graphics/xinput-<u></u>calibrator/pointercal-xinput/<u></u>pointercal.xinput<br>
meta/recipes-graphics/tslib/<u></u>tslib/ts.conf<br>
<br>
<br>
Possibly also:<br>
meta/recipes-core/init-<u></u>ifupdown/init-ifupdown-1.0<br>
meta/recipes-connectivity/<u></u>connman/connman-conf<br>
meta/recipes-connectivity/<u></u>bluez5/bluez5/bluetooth.conf<br>
meta/recipes-bsp/apmd/apmd-3.<u></u>2.2-14/apmd_proxy.conf<br>
<br>
Comment, thoughts, ...<br>
<br>
Thanks<span class="HOEnZb"><font color="#888888"><br>
-- <br>
Sau!<br>
<br>
Saul Wold<br>
Yocto Component Wrangler @ Intel<br>
Yocto Project / Poky Build System<br>
<br>
-- <br>
______________________________<u></u>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.<u></u>openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" target="_blank">http://lists.openembedded.org/<u></u>mailman/listinfo/openembedded-<u></u>core</a><br>
</font></span></blockquote></div><br></div>