From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mike Looijmans <mike.looijmans@topic.nl>,
"Burton, Ross" <ross.burton@intel.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Re-add piglit to sdk images
Date: Wed, 19 Oct 2016 16:14:21 +0100 [thread overview]
Message-ID: <1476890061.2166.75.camel@linuxfoundation.org> (raw)
In-Reply-To: <c80b8055-3c0c-4047-ebfd-4c94f41f95ba@topic.nl>
On Wed, 2016-10-19 at 16:02 +0200, Mike Looijmans wrote:
> On 19-10-16 14:53, Burton, Ross wrote:
> >
> >
> > On 18 October 2016 at 22:21, Paul Eggleton <paul.eggleton@linux.int
> > el.com
> > <mailto:paul.eggleton@linux.intel.com>> wrote:
> >
> > > > Q: Do I need to declare a runtime dependency that typically
> > comes
> > > > from busybox (tar)?
> > >
> > > Yes, because some people try to eliminate busybox from their
> > image.
> >
> > How would one express such a dependency though, given that it
> > could come from
> > tar or busybox? "Virtual" runtime dependencies aren't allowed
> > except through
> > our somewhat awkward VIRTUAL-RUNTIME convention, but that
> > probably isn't
> > warranted here.
> >
> > busybox could RRPOVIDE tar?
> If we go down that road, we'd end up with a busybox that RPROVIDES a
> hundred
> and one utilities. I doubt anyone will be happy with that...
We've come across this problem before. It is something which is
probably worth looking at to see what options we have but it is
probably a tangential issue to the patch at hand.
Cheers,
Richard
prev parent reply other threads:[~2016-10-19 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 18:31 [PATCH 0/2] Re-add piglit to sdk images Jussi Kukkonen
2016-10-14 18:32 ` [PATCH 1/2] piglit: Package tests in compressed form as well Jussi Kukkonen
2016-10-14 18:32 ` [PATCH 2/2] core-tools-testapps: Re-add piglit Jussi Kukkonen
2016-10-18 15:13 ` [PATCH 0/2] Re-add piglit to sdk images Randy MacLeod
2016-10-18 21:21 ` Paul Eggleton
2016-10-19 12:53 ` Burton, Ross
2016-10-19 14:02 ` Mike Looijmans
2016-10-19 15:08 ` Burton, Ross
2016-10-19 15:14 ` 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=1476890061.2166.75.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox