From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RPROVIDES problem for kdepimpi
Date: Fri, 21 Mar 2008 15:57:52 +0100 [thread overview]
Message-ID: <fs0idg$j6$1@ger.gmane.org> (raw)
In-Reply-To: <47E3C6F7.8030902@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Junqian Gordon Xu schreef:
| Similar to the tzdata problem. kdepimpi recipe does not define a package
| ${PN}, and bitbake doesn't like the fact that ${PN} is missing in
RPROVIDES.
|
| Should we ship an empty kdepimpi? Or any better solution?
kdepimpi-x11 does:
PACKAGES = "libmicrokcal-x11 libmicrokabc-x11 kopi-applet-x11 kopi-x11
kapi-x11 libmicrokdelibs-x11 kammu-x11 libmicrokammu-x11"
Which is buggy, since it will break the -dev and -dbg depchains (and
ships no .debug files).
Change that to:
PACKAGES += " \
libmicrokcal-x11 libmicrokcal-x11-dbg libmicrokcal-x11-dev \
libmicrokabc-x11 libmicrokabc-x11-dbg libmicrokabc-x11-dev\
kopi-applet-x11 kopi-applet-x11-dbg kopi-applet-x11-dev\
kopi-x11 kopi-x11-dbg kopi-x11-dev\
kapi-x11 kapi-x11-dbg kapi-x11-dev\
libmicrokdelibs-x11 libmicrokdelibs-x11-dbg libmicrokdelibs-x11-dev\
kammu-x11 kammu-x11-dbg\
libmicrokammu-x11 libmicrokammu-x11-dbg libmicrokammu-x11-dev"
ALLOW_EMPTY_${PN} = "1"
RDEPENDS_${PN} = "kopi-applet-x11 kopi-x11 kapi-x11 kammu-x11"
FILES_....-dev
FILES_....-dbg
etc.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH48zwMkyGM64RGpERAq/fAJ9J9UHDj/GWLoxLn+39CUFnG6XdtACgqvZP
PfvptGphDh4wh1dbRBofUgQ=
=fUrC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-21 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 14:32 RPROVIDES problem for kdepimpi Junqian Gordon Xu
2008-03-21 14:57 ` Koen Kooi [this message]
2008-03-21 15:46 ` Holger Freyther
2008-03-21 16:02 ` Junqian Gordon Xu
2008-03-21 18:42 ` Richard Purdie
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='fs0idg$j6$1@ger.gmane.org' \
--to=koen@dominion.kabel.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.