From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: <rant>the current yocto FAQ is pretty much valueless</rant>
Date: Tue, 26 Jun 2012 18:09:26 +0100 [thread overview]
Message-ID: <1447441.xnbSj4QHNd@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1206261304290.6025@oneiric>
On Tuesday 26 June 2012 13:05:21 Robert P. J. Day wrote:
> On Tue, 26 Jun 2012, Paul Eggleton wrote:
> > On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote:
> > > 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"
> >
> > OK, looking at the settings you've listed, I think these are the
> > kinds of things that site.conf was invented for - stuff that is
> > specific not to the builds you are doing but to the host machine /
> > site. You can simply put these settings in a file called site.conf
> > next to local.conf and they'll be read from there; for new build
> > directories you can just copy it in or symlink it from some common
> > location.
>
> that still requires just a touch of user intervention. no totally
> automatic way to do that, then? it's at least an improvement over
> manual copying, thanks.
I have thought about this - it would be great if oe-init-build-env could
copy/symlink your customised version from somewhere automatically every time;
however the question would be how would it know where to copy it from? I'm not
sure an added command-line option would be much better than just getting
people to copy/symlink it in manually.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-26 17:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 9:09 <rant>the current yocto FAQ is pretty much valueless</rant> Robert P. J. Day
2012-06-26 9:35 ` Jack Mitchell
2012-06-26 9:55 ` Tomas Frydrych
2012-06-26 10:09 ` Paul Eggleton
2012-06-26 10:18 ` Robert P. J. Day
2012-06-26 15:46 ` Darren Hart
2012-06-26 16:06 ` Paul Eggleton
2012-06-26 16:38 ` Tomas Frydrych
2012-06-26 16:53 ` Robert P. J. Day
2012-06-26 17:18 ` Tomas Frydrych
2012-06-26 17:59 ` Brian Duffy
2012-06-27 9:39 ` Tomas Frydrych
2012-06-26 18:52 ` Tim Bird
2012-06-27 9:09 ` Tomas Frydrych
2012-06-27 14:59 ` Koen Kooi
2012-06-27 16:43 ` Chris Hallinan
2012-06-27 17:27 ` Koen Kooi
2012-06-27 20:14 ` Tomas Frydrych
2012-06-27 21:58 ` Koen Kooi
2012-06-28 7:44 ` Tomas Frydrych
2012-07-01 16:23 ` Philip Balister
2012-06-27 21:14 ` Philip Balister
2012-06-27 21:51 ` Philip Balister
2012-06-26 11:29 ` Koen Kooi
2012-06-26 14:40 ` Rifenbark, Scott M
2012-06-26 15:45 ` Robert P. J. Day
2012-06-26 15:50 ` Rifenbark, Scott M
2012-06-26 16:18 ` Paul Eggleton
2012-06-26 16:26 ` Robert P. J. Day
2012-06-26 16:33 ` Paul Eggleton
2012-06-26 16:51 ` Robert P. J. Day
2012-06-26 17:02 ` Paul Eggleton
2012-06-26 17:05 ` Robert P. J. Day
2012-06-26 17:09 ` Paul Eggleton [this message]
2012-06-26 17:14 ` Robert P. J. Day
2012-06-26 17:08 ` Rifenbark, Scott M
2012-06-26 17:12 ` Robert P. J. Day
2012-06-27 16:42 ` Jeff Osier-Mixon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1447441.xnbSj4QHNd@helios \
--to=paul.eggleton@linux.intel.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.