From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: is "fakeroot" still used as a variable "flag"?
Date: Sun, 01 Apr 2012 00:46:43 +0100 [thread overview]
Message-ID: <1607664.qKyoFqIBt3@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1203311910320.12870@oneiric>
On Saturday 31 March 2012 19:12:12 Robert P. J. Day wrote:
> the bitbake manual lists "fakeroot" as a possible variable flag,
> along with things like "nostamp", "noexec" and so on. but i don't see
> fakeroot being used as a flag anywhere in the source tree. has that
> changed?
No, fakeroot is still used - it is a flag for functions indicating fakeroot
(these days pseudo) should be enabled when the function is executed.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-31 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 23:12 is "fakeroot" still used as a variable "flag"? Robert P. J. Day
2012-03-31 23:46 ` Paul Eggleton [this message]
2012-03-31 23:52 ` Robert P. J. Day
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=1607664.qKyoFqIBt3@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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