From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: virtual/fakeroot-native misleading
Date: Mon, 06 Jan 2014 11:49:18 +0000 [thread overview]
Message-ID: <1389008958.22784.3.camel@ted> (raw)
In-Reply-To: <52C9DA4D.5010807@vollmann.ch>
On Sun, 2014-01-05 at 23:18 +0100, Detlef Vollmann wrote:
> Trying to bitbake essentially anything requires virtual/fakeroot-native.
> But saying 'ASSUME_PROVIDED += "virtual/fakeroot-native"' because we
> have fakeroot on our machine doesn't work, as bitbake.conf explicitely
> requires pseudo. So it would be better to drop virtual/fakeroot-native
> and just require pseudo.
The virtual/ namespace exists from previous days and its true that
pseudo can do anything fakeroot could do so in that sense its valid. The
opposite is not true however as you've found out.
So technically, yes, we now require pseudo-native and we could go and
change those dependencies. Its not exactly a pressing issue but I'd take
patches.
Cheers,
Richard
prev parent reply other threads:[~2014-01-06 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 22:18 virtual/fakeroot-native misleading Detlef Vollmann
2014-01-06 11:49 ` Richard Purdie [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=1389008958.22784.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-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.