<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>4011</bug_id>
          
          <creation_ts>2013-03-11 21:12:31 +0000</creation_ts>
          <short_desc>Merge machine specific config recipes into one recipe to rule them all</short_desc>
          <delta_ts>2026-05-21 15:29:06 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>5.99</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          <see_also>http://bugzilla.yoctoproject.org/show_bug.cgi?id=6362</see_also>
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>   </status_whiteboard>
          <keywords></keywords>
          <priority>Low</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>Future</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Richard Purdie">richard.purdie</reporter>
          <assigned_to name="Unassigned">unassigned</assigned_to>
          <cc>akuster</cc>
    
    <cc>alexandru.c.georgescu</cc>
    
    <cc>dvhart</cc>
    
    <cc>jose.perez.carranza</cc>
    
    <cc>mark.hatle</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>randy.macleod</cc>
    
    <cc>ross.burton</cc>
    
    <cc>srifenbark</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>30630</commentid>
    <comment_count>0</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-03-11 21:12:31 +0000</bug_when>
    <thetext>We currently have a lot of individual recipes installing single machine specific files. We need to combine these to be installed by a single recipe which still creates all the relavent individual recipes.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43525</commentid>
    <comment_count>1</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2014-05-22 19:43:36 +0000</bug_when>
    <thetext>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&apos;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&apos;s bluetooth.com
apmd_proxy.conf

Anything I missed?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43526</commentid>
    <comment_count>2</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2014-05-22 19:47:25 +0000</bug_when>
    <thetext>keymaps, alsa-state, pointercal, pointercal-xinput, come to mind</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>43577</commentid>
    <comment_count>3</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2014-05-23 22:33:15 +0000</bug_when>
    <thetext>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 = &quot;${PN}-conf&quot;
      # Can be overriden in recipe
      CONFFILES_conffiles ?= &quot;${PN}.conf&quot;
  - Will provide files not needed on final image, small
    amount of extra space used.    

2) 1 package / conf file (${PN}-conf)
  - exactly what&apos;s needed will be installed
  - no needs for additional RPROVIDES
  - More packaging overhead, package data might be bigger than actual contents!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>51400</commentid>
    <comment_count>4</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2015-06-01 21:22:07 +0000</bug_when>
    <thetext>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 &quot;Configuration Files&quot; 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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85941</commentid>
    <comment_count>5</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2019-12-22 21:22:49 +0000</bug_when>
    <thetext>is this still an issue?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>86433</commentid>
    <comment_count>6</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2020-02-13 16:18:53 +0000</bug_when>
    <thetext>Is still a valid issue.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>