All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/40] Review and ACK
Date: Thu, 18 Jul 2013 12:15:23 +0100	[thread overview]
Message-ID: <1374146123.6324.5.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1400703.GdJurTDMZr@helios>

On Thu, 2013-07-18 at 12:01 +0100, Paul Eggleton wrote:
> On Thursday 18 July 2013 11:52:22 Burton, Ross wrote:
> > On 18 July 2013 07:34, Saul Wold <sgw@linux.intel.com> wrote:
> > >   valgrind: added perl dependency
> > 
> > I presume the situation here is that a target perl wasn't actually
> > built, so adding an explicit runtime dependency causes it to be built
> > and therefore available in the feed for rpm to find.
> > 
> > To me this says that the #!-to-dependency magic from rpmdeps isn't
> > really useful, as we then have to go and put explicit dependencies
> > back in to ensure the requirements are actually built.
> 
> I have to say I too have wondered this. Perhaps these would be better 
> implemented as QA warnings (that could be defaulted to errors) rather than 
> just silently adding the dependencies.

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?

p.




  reply	other threads:[~2013-07-18 11:15 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 [this message]
2013-07-18 11:35       ` Burton, Ross
2013-07-18 12:16         ` Paul Eggleton
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=1374146123.6324.5.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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 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.