From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RDEPENDS_${PN}-dev = ${PN} badness
Date: Thu, 17 Apr 2008 22:00:43 +0200 [thread overview]
Message-ID: <fu8a9b$ces$1@ger.gmane.org> (raw)
In-Reply-To: <20080417175150.GJ31895@buddha.tw.openmoko.com>
John Lee wrote:
> Hi,
>
> Take gtk-doc-dev for example:
>
> The gtk-doc package is empty, so it will not be created. However, if
> you install gtk-doc-dev, it RDEPENDS on gtk-doc, which cannot be
> found. The install will fail.
>
> I think we should use
>
> RRECOMMENDS_${PN}-dev = "${PN} (= ${DEBPV})"
>
> instead.
ALLOW_EMPTY_${PN} = "1" would be a better idea, and in line without
other depchain workarounds.
regards,
Koen
>
> We (Julian Chu and me) found this when digging the cause of
> meta-toolchain-openmoko build failure. task-openmoko-toolchain-target
> contains quite a few -dev packages in it, so the opkg-cl install will
> fail. The log looks something like this:
>
> ERROR: Cannot satisfy the following dependencies for
> task-openmoko-toolchain-target: gtk-doc (= 1.0-r1)
> util-macros (= 1:1.1.5-r1) renderproto (= 1:0.9.3-r0) xproto
> (= 1:7.0.10-r1) bigreqsproto (= 1:1.0.2-r1) xextproto (=
> 1:7.0.2-r1) xtrans (= 1:1.0.4-r0) xcmiscproto (= 1:1.1.2-r1)
> xf86bigfontproto (= 1:1.1.2-r1) kbproto (= 1:1.0.3-r1)
> inputproto (= 1:1.4.2.1-r0) fixesproto (= 1:4.0-r1)
> xineramaproto (= 1:1.1.2-r1) randrproto (= 1:1.2.1-r1)
> compositeproto (= 1:0.4-r0) damageproto (= 1:1.1.0-r1)
>
> Similiar symptoms can be found in the packages above.
>
> Regards,
> John
next prev parent reply other threads:[~2008-04-17 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 17:51 RDEPENDS_${PN}-dev = ${PN} badness John Lee
2008-04-17 20:00 ` Koen Kooi [this message]
2008-04-17 23:24 ` Richard Purdie
2008-04-19 11:07 ` Michael 'Mickey' Lauer
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='fu8a9b$ces$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.