From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: is there really a "fakeroot" task flag?
Date: Tue, 17 Jul 2012 12:48:30 -0500 [thread overview]
Message-ID: <5005A56E.2090300@windriver.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207171340560.7173@oneiric>
On 7/17/12 12:41 PM, Robert P. J. Day wrote:
> On Tue, 17 Jul 2012, Mark Hatle wrote:
>
>> On 7/17/12 9:55 AM, Robert P. J. Day wrote:
>>>
>>> perusing bitbake user manual and in section 2.1.18, "Task Flags",
>>> there's mention of "fakeroot". that's not really a task flag, is it?
>>> i thought that that's (now?) a keyword that's used to define a task
>>> with that property.
>>>
>>> is that line in the user manual incorrect?
>>
>> My understanding is this is a key word that gets turned into a task
>> flag.
>
> ok, that makes sense. that's just not clear from that section in
> the bitbake manual. are there any other special cases like that?
I believe that both "fakeroot" and "python" are the two only two inline "task
flags".
--Mark
> rday
>
next prev parent reply other threads:[~2012-07-17 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 14:55 is there really a "fakeroot" task flag? Robert P. J. Day
2012-07-17 17:12 ` Mark Hatle
2012-07-17 17:41 ` Robert P. J. Day
2012-07-17 17:48 ` Mark Hatle [this message]
2012-07-17 18:08 ` Robert P. J. Day
2012-07-17 18:40 ` Mark Hatle
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=5005A56E.2090300@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox