* possible content for site.conf?
@ 2017-03-22 10:51 Robert P. J. Day
2017-03-22 10:54 ` Burton, Ross
2017-03-22 22:32 ` Douglas Royds
0 siblings, 2 replies; 6+ messages in thread
From: Robert P. J. Day @ 2017-03-22 10:51 UTC (permalink / raw)
To: OE Core mailing list
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
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: possible content for site.conf?
2017-03-22 10:51 possible content for site.conf? Robert P. J. Day
@ 2017-03-22 10:54 ` Burton, Ross
2017-03-22 11:02 ` Robert P. J. Day
2017-03-22 22:32 ` Douglas Royds
1 sibling, 1 reply; 6+ messages in thread
From: Burton, Ross @ 2017-03-22 10:54 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: OE Core mailing list
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
On 22 March 2017 at 10:51, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> 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?
>
That's pretty much the expected use.
Ross
[-- Attachment #2: Type: text/html, Size: 888 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: possible content for site.conf?
2017-03-22 10:54 ` Burton, Ross
@ 2017-03-22 11:02 ` Robert P. J. Day
2017-03-23 2:30 ` Mark Hatle
0 siblings, 1 reply; 6+ messages in thread
From: Robert P. J. Day @ 2017-03-22 11:02 UTC (permalink / raw)
To: Burton, Ross; +Cc: OE Core mailing list
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Wed, 22 Mar 2017, Burton, Ross wrote:
>
> On 22 March 2017 at 10:51, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> 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?
>
>
> That's pretty much the expected use.
i thought so ... i wracked my brain trying to think what else
belonged in there, and that's all i came up with. thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: possible content for site.conf?
2017-03-22 10:51 possible content for site.conf? Robert P. J. Day
2017-03-22 10:54 ` Burton, Ross
@ 2017-03-22 22:32 ` Douglas Royds
1 sibling, 0 replies; 6+ messages in thread
From: Douglas Royds @ 2017-03-22 22:32 UTC (permalink / raw)
To: OE Core mailing list
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 1967 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: possible content for site.conf?
2017-03-22 11:02 ` Robert P. J. Day
@ 2017-03-23 2:30 ` Mark Hatle
2017-03-23 9:52 ` Robert P. J. Day
0 siblings, 1 reply; 6+ messages in thread
From: Mark Hatle @ 2017-03-23 2:30 UTC (permalink / raw)
To: openembedded-core
On 3/22/17 7:02 PM, Robert P. J. Day wrote:
> On Wed, 22 Mar 2017, Burton, Ross wrote:
>
>>
>> On 22 March 2017 at 10:51, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>> 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?
>>
>>
>> That's pretty much the expected use.
>
> i thought so ... i wracked my brain trying to think what else
> belonged in there, and that's all i came up with. thanks.
I have seen people do some blacklist entries here (or preferred version) when
they have a company policy not to use certain software. (Similarly a site wide
PACKAGECONFIG to disable a feature that isn't allowed.)
--Mark
> rday
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: possible content for site.conf?
2017-03-23 2:30 ` Mark Hatle
@ 2017-03-23 9:52 ` Robert P. J. Day
0 siblings, 0 replies; 6+ messages in thread
From: Robert P. J. Day @ 2017-03-23 9:52 UTC (permalink / raw)
To: Mark Hatle; +Cc: openembedded-core
On Thu, 23 Mar 2017, Mark Hatle wrote:
> On 3/22/17 7:02 PM, Robert P. J. Day wrote:
> > On Wed, 22 Mar 2017, Burton, Ross wrote:
> >
> >>
> >> On 22 March 2017 at 10:51, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >> 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?
> >>
> >>
> >> That's pretty much the expected use.
> >
> > i thought so ... i wracked my brain trying to think what else
> > belonged in there, and that's all i came up with. thanks.
>
> I have seen people do some blacklist entries here (or preferred
> version) when they have a company policy not to use certain
> software. (Similarly a site wide PACKAGECONFIG to disable a feature
> that isn't allowed.)
ah, yes, good points, thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-03-23 9:52 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-22 10:51 possible content for site.conf? Robert P. J. Day
2017-03-22 10:54 ` Burton, Ross
2017-03-22 11:02 ` Robert P. J. Day
2017-03-23 2:30 ` Mark Hatle
2017-03-23 9:52 ` Robert P. J. Day
2017-03-22 22:32 ` Douglas Royds
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.