Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: update-rc.d: don't add runtime dependency if not doing	online package management; only add it to ${PN} in any case.
Date: Wed, 17 Jun 2009 17:41:04 -0400	[thread overview]
Message-ID: <20090617214104.GC21132@denix.org> (raw)
In-Reply-To: <1245224450.29153.99.camel@lenovo.internal.reciva.com>

On Wed, Jun 17, 2009 at 08:40:50AM +0100, Phil Blundell wrote:
> On Wed, 2009-06-17 at 00:29 -0400, Denys Dmytriyenko wrote:
> > The problem comes from the fact that either RDEPENDS_{PN}_append = "blah" or 
> > RDEPENDS_{PN} += "blah" used in the class overwrite the value set in 
> > inheriting recipe, instead of appending to it. The position of the inherit 
> > command in the recipe relative to its own RDEPENDS does not matter. And I 
> > don't think this issue only applies to RDEPENDS variable...
> 
> I've checked in a change to udev-141 that I think should fix this.
> (Other versions didn't seem to be affected.)  Please give that a go and
> see if it works for you now.

Hmm, it works, thanks! I was pretty sure I tried this before I sent out my 
email...

Any ideas why RDEPENDS_{PN} in "udev" recipe works, but RDEPENDS_udev doesn't? 
It only happens with inherit update-rc.d.bbclass, which also changes 
RDEPENDS_{PN}... I have the same issue with my own recipes, which I need to 
fix similarly.

-- 
Denys



  reply	other threads:[~2009-06-19  0:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  4:29 update-rc.d: don't add runtime dependency if not doing online package management; only add it to ${PN} in any case Denys Dmytriyenko
2009-06-17  7:40 ` Phil Blundell
2009-06-17 21:41   ` Denys Dmytriyenko [this message]
2009-06-19  7:36     ` Phil Blundell
2009-06-20 10:08       ` Phil Blundell
2009-06-20 15:21         ` Christopher Larson
2009-06-20 17:19           ` Koen Kooi
2009-06-20 17:32             ` 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=20090617214104.GC21132@denix.org \
    --to=denis@denix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox