All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: some questions about bitbake user manual, fetching chapter
Date: Tue, 17 Jun 2014 10:12:42 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1406170936190.619@localhost> (raw)


  working my way thru the fetching chapter, some questions:

* manual doesn't explain what happens if you don't supply *both*
checksums for downloading -- what if you supply only one? or both
and one is correct while the other is incorrect? i think this would
be useful info for the reader.

* right now, manual says FILESDIR is still "deprecated". is it just
deprecated, or is it at the point where it can be killed outright?
currently, there's nothing in the entire poky checkout that uses it.
have people been given sufficient warning at this point?

* i asked about this a long time ago -- in section 4.3.1 (local file
fetcher), there's an alleged sample line:

 SRC_URI = "file://relativefile.patch;this=ignored"

"this=ignored"? can that be replaced by, say, a sample line involving
"apply=yes" or "apply=no"? or any other relevant examples?

  i think that's it for now.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



             reply	other threads:[~2014-06-17 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 14:12 Robert P. J. Day [this message]
2014-06-18 14:35 ` some questions about bitbake user manual, fetching chapter 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.1406170936190.619@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.