All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/40] Review and ACK
Date: Thu, 18 Jul 2013 13:16:31 +0100	[thread overview]
Message-ID: <2691932.dGi55gTP8y@helios> (raw)
In-Reply-To: <CAJTo0La1=YTa2rXasY2LhRkA0O4-uV0UDUUGUc-0kNrLasX83A@mail.gmail.com>

On Thursday 18 July 2013 12:35:04 Burton, Ross wrote:
> On 18 July 2013 12:15, Phil Blundell <pb@pbcl.net> wrote:
> > Seeing this discussion makes me wonder: if the target perl hasn't
> > actually been built at this point, how does rpmdeps know what package to
> > add a dependency on in the first place?  Does it just have some random
> > hard-coded list somewhere?
> 
> It adds a dependency on /usr/bin/perl as a file, not perl itself, as
> the error is "no package provides /usr/bin/perl".

Right, and at the moment this only works for RPM; I'm not sure if any of the 
others natively support file-based dependencies like this.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-07-18 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  6:34 [CONSOLIDATED PULL 00/40] Review and ACK Saul Wold
2013-07-18  9:43 ` Paul Eggleton
2013-07-18 12:04   ` Otavio Salvador
2013-07-18 14:13   ` Saul Wold
2013-07-18 10:52 ` Burton, Ross
2013-07-18 11:01   ` Paul Eggleton
2013-07-18 11:15     ` Phil Blundell
2013-07-18 11:35       ` Burton, Ross
2013-07-18 12:16         ` Paul Eggleton [this message]
2013-07-18 12:26           ` Phil Blundell

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=2691932.dGi55gTP8y@helios \
    --to=paul.eggleton@linux.intel.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 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.