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 <rpj...@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
========================================================================
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
