Creating a machine specific recipe for config file

[Saul Wold <sgw@linux.intel.com>]

Folks,

We have had an open enhancement in the form of bugzilla #4011 
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=4011).

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.

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.

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!

Currently the list of recipes/config files affected include:


meta/recipes-bsp/pointercal/pointercal/*/pointercal
meta/recipes-bsp/formfactor/files/*/machconfig
meta/recipes-bsp/alsa-state/alsa-state/asound.conf
meta/recipes-graphics/xorg-xserver/xserver-xf86-config/*/xorg.conf
meta/recipes-bsp/keymaps/files/keymap.sh
meta/recipes-graphics/xinput-calibrator/pointercal-xinput/pointercal.xinput
meta/recipes-graphics/tslib/tslib/ts.conf


Possibly also:
meta/recipes-core/init-ifupdown/init-ifupdown-1.0
meta/recipes-connectivity/connman/connman-conf
meta/recipes-connectivity/bluez5/bluez5/bluetooth.conf
meta/recipes-bsp/apmd/apmd-3.2.2-14/apmd_proxy.conf

Comment, thoughts, ...

Thanks
-- 
     Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System