From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Question about bluez4 and PROVIDES_append_angstrom
Date: Thu, 22 Oct 2009 21:24:07 +0200 [thread overview]
Message-ID: <4AE0B157.80807@gmail.com> (raw)
Hello,
first of all I must say that I am not a OE expert and I'd like to learn
and understand, so please apologize if my question is too silly for most
of you :-)
I am quite confused about a few lines I found into the following files.
The result of these lines faced me to errors using KaeilOS distro.
This modification looks (to me) related to bluez4 and Angstrom only and
I wonder why some package recipes (bluez4*.bb) contains some lines that
strictly ties them to Angstrom distribution breaking other distributions.
Files I found are the following:
recipes/bluez/bluez4_4.35.bb:PROVIDES_append_angstrom =
" bluez-utils bluez-libs"
recipes/bluez/bluez4_4.37.bb:PROVIDES_append_angstrom =
" bluez-utils bluez-libs"
recipes/bluez/bluez4.inc:PROVIDES_append_angstrom =
" bluez-utils-dbus bluez-utils bluez-libs"
Lines are similar to these:
# For angstrom we want this to replace at least bluez-libs
PROVIDES_append_angstrom = " bluez-utils-dbus bluez-utils bluez-libs"
RPROVIDES_bluez4-dev_angstrom = "bluez-libs-dev"
My question is: why these lines are not into angstrom*.bb distro recipe
making bluez*.bb distro-independent (agnostic)?
Thank you in advance for your hints.
/marco
next reply other threads:[~2009-10-22 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 19:24 Marco Cavallini [this message]
2009-10-22 19:36 ` Question about bluez4 and PROVIDES_append_angstrom Denys Dmytriyenko
2009-10-22 20:33 ` Koen Kooi
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=4AE0B157.80807@gmail.com \
--to=koansoftware@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 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.