On Tue, 26 Jun 2012, Paul Eggleton wrote:
> On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote:
> > i thought that was the technique for centralizing personal config
> > preferences that you *didn't* want to manually copy into every
> > local.conf file you created. if you add that personal content into
> > each local.conf, then of course you don't need those options.
>
> I guess it depends on what you mean by "personal content". Certain
> settings are really part of distro policy and if you're finding that
> you're setting them all the time for all of the builds that you're
> doing, it would make more sense to create a distro layer that sets
> them - then it's simply a matter of ensuring that layer is added to
> your bblayers.conf and you set DISTRO as appropriate.
>
> AFAIK the command line options in question were added to allow
> frontends to inject configuration into bitbake rather than something
> the user would normally use directly.
ok, that makes sense. but would it also make sense for bitbake to
perhaps support another option that *does* allow personal content to,
say, be effectively appended to one's local.conf. for instance, every
single local.conf i create immediately gets this added to the end:
SOURCE_MIRROR_URL ?= "file:///home/rpjday/dl/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
# BB_NO_NETWORK = "1"
is there a simpler way to do that?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
