From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake-user-manual-intro.xml: Semantic cleanup, clarifications.
Date: Wed, 18 Jun 2014 11:13:45 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406181111280.28862@localhost> (raw)
In-Reply-To: <1413867.iP4Nqeb177@peggleto-mobl5.ger.corp.intel.com>
On Wed, 18 Jun 2014, Paul Eggleton wrote:
> On Wednesday 18 June 2014 08:38:04 Robert P. J. Day wrote:
> > @@ -413,6 +414,18 @@
> > you have a directory entitled
> > <filename>bitbake-1.17.0</filename>.
> > </para></listitem>
> > + <listitem><para><emphasis>Using the BitBake that comes with
> > your build checkout:</emphasis> + A final possibility
> > for getting a copy of BitBake is that it + already comes
> > with your checkout of a larger Bitbake-based build system, +
> > such as Poky or Yocto Project. Rather than manually checking out +
> > individual layers and gluing them together yourself, you can
> > check + out an entire build system such as Poky with
> > something like: + <literallayout class='monospaced'>
> > + $ git clone git://git.yoctoproject.org/poky
> > + </literallayout>
> > + where that checkout will already include a version of
> > BitBake which + has been thoroughly tested for
> > compatibility with the other components. +
> > </para></listitem>
> > </itemizedlist>
> > </para>
> > </section>
>
> Ignoring the mangling that my email client has done, I'm hesitant
> about the latter change. I appreciate the intention and what you've
> added isn't incorrect per se, but the pointer to actually check out
> poky might be a bit too much - I'd rather see a pointer to a
> different document (perhaps the Yocto Project Quick Start guide?).
> Additionally poky doesn't completely free you from fetching and
> incorporating individual layers, just OE-Core / meta-yocto /
> meta-yocto-bsp.
i see your point, but i still think the reader should at least be
aware that, under normal(?) circumstances, they might not need to go
hunting around for bitbake as they might already have it. i'm totally
open to anyone wanting to reword that.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-06-18 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 12:38 [PATCH] bitbake-user-manual-intro.xml: Semantic cleanup, clarifications Robert P. J. Day
2014-06-18 14:56 ` Paul Eggleton
2014-06-18 15:13 ` Robert P. J. Day [this message]
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=alpine.LFD.2.11.1406181111280.28862@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.