All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rifenbark, Scott M" <scott.m.rifenbark@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: bitbake user manual: "Variable Flags" section seems to need updating
Date: Thu, 26 Jun 2014 22:08:29 -0700	[thread overview]
Message-ID: <53ACFC4D.4020805@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1406221041150.4008@localhost>

I will need information from somebody that understands what these 
undocumented flags do.  Anyone?

Thanks,
Scott

On 6/22/2014 7:47 AM, Robert P. J. Day wrote:
>    the "Variable Flags" section of the bitbake user manual seems to be
> incomplete:
>
> http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#variable-flags
>
> at the very least, i see additional task flags such as "selfstamp",
> "lockfiles", "stamp-base" and more, just from having stumbled across
> this:
>
> lib/toaster/orm/fixtures/orm_views_testdata.json:
> "variable_value": "doc defaultval _append _prepend deps depends
> lockfiles type vardepsexclude vardeps vardepvalue file-checksums
> python func task export unexport noexec nostamp dirs cleandirs
> sstate-lockfile-shared prefuncs postfuncs export_func deptask rdeptask
> recrdeptask nodeprrecs stamp-base stamp-extra-info",
>
> but i don't know enough about some of those flags to know what to add
> for them (if anything).
>
> rday
>



      reply	other threads:[~2014-06-27  5:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22 14:47 bitbake user manual: "Variable Flags" section seems to need updating Robert P. J. Day
2014-06-27  5:08 ` Rifenbark, Scott M [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=53ACFC4D.4020805@linux.intel.com \
    --to=scott.m.rifenbark@linux.intel.com \
    --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.