[OE-core] possible content for site.conf?

[Douglas Royds]

We use it as a form of default local.conf, making it a consistent 
configuration for building our layer. By combining this with a "bb" 
wrapper script, nothing needs to be sourced, and there is no build 
preparation at all - our workflow is simply

 1. Check out our layer
 2. Type `bb thing`

The wrapper-script and site.conf handle the rest. Our site.conf contains 
the things you name, plus most of the settings from local.conf.sample, 
plus automatically-computed paths to directories:

  * OEDIR
      o The one that contains the build/ directory
  * META_OURLAYERNAME
  * SCRIPTS
  * SOURCEDIR
      o Where all the external sources get automatically checked out

Devs don't have to have a local.conf at all. The local.conf becomes a 
place to put, well, local configuration.


On 22/03/17 23:51, Robert P. J. Day wrote:

>    i'm documenting what one might *properly* put in a site.conf file,
> since i've been seeing examples of people loading it with references
> to recipes and images and so on, which is totally inappropriate.
>
>    from site.conf.sample, the obvious content is things like:
>
> * download dir
> * reference to local (in-house) source mirror
> * http proxies/fetching configuration
>
> and so on. any other things people throw into site.conf i can just add
> to a list so readers can understand what that file is truly designed
> for?
>
> rday
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170323/0a7dbfe2/attachment-0002.html>