Re: [CONSOLIDATED PULL 00/40] Review and ACK

[Phil Blundell <pb@pbcl.net>]

On Thu, 2013-07-18 at 13:16 +0100, Paul Eggleton wrote:
> 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.

I'm pretty sure neither opkg nor dpkg has any concept of depending on a
file.  

I guess if rpmdeps outputs that data then it would be possible for logic
in package.bbclass to then figure out which package contains the
depended-on file and either add a dependency or generate an error if
nothing that contains that file has been built.

p.