From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Christopher Larson <clarson@kergoth.com>
Cc: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: should list of "Variable Flags" include "fakeroot"?
Date: Wed, 9 Jul 2014 11:25:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407091123270.10635@localhost> (raw)
In-Reply-To: <CABcZAN=OPjSrfQNSjarThUu37Q3LgoZc8jvX4t1+CN8nZnEh=w@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1468 bytes --]
On Wed, 9 Jul 2014, Christopher Larson wrote:
>
> On Wed, Jul 9, 2014 at 6:38 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> user manual, "3.6 Variable Flags" includes "fakeroot" as one of the
> numerous flags, but that section claims that all of those flags can be
> set using the standard variable syntax. but IIRC, fakeroot is set as
> an *attribute* on tasks these days, as in:
>
> fakeroot tar_sdk() {
>
> so how should that entry be worded/reworded? unless i'm misreading
> something.
>
>
> It likely shouldn't be mentioned as a flag. The fact that it's a
> flag internally is a bitbake implementation detail that likely isn't
> something they need to be aware of, in my personal opinion, anyway.
that's the way i read it ... all the underlying support code still
treats it as a "flag", but since i see no usage of it with the flag
syntax, i'll just submit a patch to delete it from the flag list,
assuming it's discussed adequately elsewhere.
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-07-09 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 13:38 should list of "Variable Flags" include "fakeroot"? Robert P. J. Day
2014-07-09 15:20 ` Christopher Larson
2014-07-09 15:25 ` 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.1407091123270.10635@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.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.