From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Question about bluez4 and PROVIDES_append_angstrom
Date: Thu, 22 Oct 2009 22:33:58 +0200 [thread overview]
Message-ID: <hbqfjn$4m0$1@ger.gmane.org> (raw)
In-Reply-To: <4AE0B157.80807@gmail.com>
On 22-10-09 21:24, Marco Cavallini wrote:
> 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"
It would only 'break' for 'other' distros if they manually enable
'angstrom' as override. If they do so, they do it at their own risk.
Some grepping shows only DISTRO=openmoko does that and I haven't heard
any complaints about bluez from those users.
Also, that override only works if you set a PREFERRED_PROVIDER as well.
Having said that, why do you keep blaming angstrom for kaelios problems?
I keep getting reports (second or third hand info, I admit) about you
badmouthing angstrom on IRC, which seems to be in fashion lately, but I
would prefer people to do badmouthing with *actual* problems instead of
projecting their own. It's not angstroms fault if you missed a few lines
when copy/pasting from it.
Koen
prev parent reply other threads:[~2009-10-22 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 19:24 Question about bluez4 and PROVIDES_append_angstrom Marco Cavallini
2009-10-22 19:36 ` Denys Dmytriyenko
2009-10-22 20:33 ` Koen Kooi [this message]
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='hbqfjn$4m0$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.