From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: is there a TODO/issues list for bitbake user manual enhancements?
Date: Fri, 20 Jun 2014 13:26:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406201322310.28485@localhost> (raw)
is there anywhere to track proposed changes to the bitbake user
manual? one of the things i've already noted is that the variable
glossary is somewhat incomplete. for example, at the very least, it
should include the following variables that are explicitly set in
bitbake's own bitbake.conf file:
CVSDIR
DEPLOY_DIR
DEPLOY_DIR_IMAGE
FILE_DIRNAME
GITDIR
IMAGE_CMD
IMAGE_ROOTFS
P
S
SVNDIR
TARGET_ARCH
TMPDIR
WORKDIR
is there a list to add these to? or is most of the effort these days
being invested in the yocto version of the ref manual?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-06-20 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 17:26 Robert P. J. Day [this message]
2014-06-27 5:05 ` is there a TODO/issues list for bitbake user manual enhancements? Rifenbark, Scott M
2014-08-06 16:51 ` Paul Eggleton
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.1406201322310.28485@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.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.