Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] recipes: conform to OE packaging guidelines with RDEPENDS/RREDEPENDS
Date: Sun, 27 Jun 2010 22:32:43 +0200	[thread overview]
Message-ID: <20100627203243.GR17650@jama> (raw)
In-Reply-To: <201006272106.36928.bluelightning@bluelightning.org>

On Sun, Jun 27, 2010 at 09:06:36PM +0100, Paul Eggleton wrote:
> On Wed, 02 Jun 2010, Martin Jansa wrote:
> > * there is probably very few cases when it's needed without _${PN},
> >   if you find one in attached patch, please enlighten me
> 
> I've just discovered this change is what has broken the build of opie-taskbar-
> images:
> 
> ------------------------------ snip --------------------------------
> paul@linc:~/oe/build-hx4700-dev$ bitbake opie-taskbar-images
> NOTE: Handling BitBake files: / (8377/8377) [100 %]
> NOTE: Parsing finished. 7570 cached, 477 parsed, 330 skipped, 0 masked.
> NOTE: Resolving any missing task queue dependencies
> ERROR: '['/home/paul/oe/org.openembedded.dev/recipes/opie-taskbar/opie-
> taskbar-images_1.2.4.bb']' RDEPENDS/RRECOMMENDS or otherwise requires the 
> runtime entity 'opie-taskbar-images' but it wasn't found in any PACKAGE or 
> RPROVIDES variables
> NOTE: Runtime target 'opie-taskbar-images' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['opie-taskbar-images']
> ERROR: Required build target 'opie-taskbar-images' has no buildable providers.
> Missing or unbuildable dependency chain was: ['opie-taskbar-images', 'opie-
> taskbar-images']
> paul@linc:~/oe/build-hx4700-dev$
> ------------------------------ snip --------------------------------
> 
> Can I revert the changes to any opie packages that have been broken? Or is 
> there an alternative solution?

Andrea Adami already asked me about it.

RPROVIDES_${PN} = "${PN}" looks a bit wrong to me and changing it back
to
RPROVIDES = "${PN}"
doesn't make it much better (more understandable in my eyes).

I found one issue in ttf-fonts
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=14c265b107725a8f7534dfb354ad12edf9f7aec3
but there it was because .inc file was setting RRECOMMENDS for all
packages and _subpackages_ including this .inc. So setting it for ${PN}
wasn't enough (and I could also add RRECOMMENDS for every subpackage really
needing this RRECOMMENDS font-update-common).

But having ${PN} on right side of assignment is a bit strange, I'm not
using/building opie, can you check why exactly it needs to be used this
way?.

-- 
Jansa 'JaMa' Martin     jabber: Martin.Jansa@gmail.com



  reply	other threads:[~2010-06-27 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 13:39 [PATCH] recipes: conform to OE packaging guidelines with RDEPENDS/RREDEPENDS Martin Jansa
2010-06-02 17:16 ` Koen Kooi
2010-06-02 17:20 ` Denys Dmytriyenko
2010-06-02 17:43   ` Martin Jansa
2010-06-27 20:06 ` Paul Eggleton
2010-06-27 20:32   ` Martin Jansa [this message]
2010-06-27 21:57     ` Phil Blundell
2010-06-27 22:17       ` Martin Jansa
2010-06-27 22:17       ` [PATCH] opie-taskbar-images: fix RPROVIDES Martin Jansa
2010-06-28 21:27         ` Andrea Adami
2010-06-28 21:55         ` Paul Eggleton

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=20100627203243.GR17650@jama \
    --to=martin.jansa@gmail.com \
    --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