When trying to understand how to use auto.conf I found some misleading steps in mega-manual: "The files site.conf and auto.conf are not created by the environment initialization script. If you want these configuration files, you must create them yourself: " So I must create auto.conf manually! Still one paragraph bellow is specified we do not create this file by our hands: " auto.conf: This file is not hand-created. Rather, the file is usually created and written to by an autobuilder. The settings put into the file are typically the same as you would find in the conf/local.conf or the conf/site.conf files. " Please clarify this in manual. Paul, could you please help?
Hi, Yes - that is confusing. I updated the wording to what I think is really going on. Paul should check it over. Here is the section in the ref-manual: http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#user-configuration. Let me know. Thanks, Scott
let this run for another month then will set to RESOLVED if no further feedback. Scott
I am ok with the modifications. Should we assign it to Paul?
Thanks Bogdan, Paul is on the CC list for this bug. I will wait a while to see if he has anything to say about the fix. Scott
I'm fairly happy with the new content. The note box does duplicate the later statement about auto.conf / site.conf containing the same sorts of settings as local.conf though, but that's not a major issue. The only thing possibly worth adding is a mention of the order in which these files are read - which is site.conf, auto.conf and then local.conf. The normal rules about the different types of assignment statement apply, but for example if you have VARIABLE = "value1" in auto.conf and VARIABLE = "value2" in local.conf, VARIABLE's value will be "value2" since local.conf gets parsed later.
See the last paragraph in http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#user-configuration and let me know if that addresses this extra point. Scott
Hi, No further comments on this. I am setting to RESOLVED and marking the doc flag to "done." Thanks, Scott
This is resolved now.