From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] libpcap: weaken bluez-libs dependency
Date: Wed, 15 Apr 2009 13:06:40 +0200 [thread overview]
Message-ID: <gs4f40$jbv$3@ger.gmane.org> (raw)
In-Reply-To: <200904151247.33585.hs4233@mail.mn-solutions.de>
On 15-04-09 12:47, Holger Schurig wrote:
>> NACK, no USE flags in OE.
>
> I'm not sure if this was a mis-design that I made.
>
> When I modeled *.bb and *.bbclass files and wrote parts of the
> initial bitbake, I thought that USE variables lead even more to
> a combinatorical explosion (think package tests!) than the
> overrides I added.
Any form of USE flags means that package QA becomes practically
impossible. I know that lots of people don't care about (package) QA,
but I do.
regards,
Koen
next prev parent reply other threads:[~2009-04-15 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 8:36 [PATCH] libpcap: weaken bluez-libs dependency Roman I Khimov
2009-04-15 9:04 ` Koen Kooi
2009-04-15 9:47 ` Roman I Khimov
2009-04-15 10:08 ` Andrea Adami
2009-04-15 10:47 ` Holger Schurig
2009-04-15 11:06 ` Koen Kooi [this message]
2009-04-15 9:24 ` Graeme Gregory
2009-04-15 9:41 ` Roman I Khimov
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='gs4f40$jbv$3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox