From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: QA Goals for OpenEmbedded
Date: Thu, 07 Jan 2010 10:40:51 +0100 [thread overview]
Message-ID: <hi4a73$gpt$2@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b11001070135v3ec3e542m892c8a0fc014f4f6@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-01-10 10:35, Frans Meulenbroeks wrote:
> 2010/1/7 Graeme Gregory <dp@xora.org.uk>:
>> On Thu, Jan 07, 2010 at 09:50:36AM +0100, Frans Meulenbroeks wrote:
>>> 2010/1/7 Graeme Gregory <dp@xora.org.uk>:
>>>> On Wed, Jan 06, 2010 at 11:09:10PM +0100, Rolf Leggewie wrote:
>>>>> allergic to COMPATIBLE_MACHINE for no particular reason). Bitbake can't
>>>>> do versioned depends and so we can't say that $bb2-$version does not
>>>>> compile with gcc less than 3.4.x, for example. Those are just two
>>>>> examples. XorA "solved" this in a hackish way with angsstrom.bbclass.
>>>>>
>>>> No he didnt and no its not a hack. Its a blacklist of packages that for
>>>> various reasons Angstrom NEVER wants built.
>>>
>>> Should we have such a blacklist per machine?
>>> My sheevaplug rungs angstrom, but as it has no display it has no need
>>> for an X server, nor for ide or pci or sata tools.
>>>
>> It follows the standard overide rules (or should do) so you should
>> be able to blacklist per machine.
>>
>> Of course you chose a bad example as I know quite a few people are using
>> the sheeva with usb displaylink adapters.
>
> Ah ok, I don't know any of them, but let's stay on safe grounds and
> take pci or sata tools as an example ;-)
You don't like usb2sata adaptors?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLRawjMkyGM64RGpERAoFSAKCds8QU/tPv0gOIpDIshm1FZ/cJVQCgnoMl
3J3CPrd7P7UyYBDhCOebPfQ=
=cmr3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-07 9:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 4:07 QA Goals for OpenEmbedded Holger Hans Peter Freyther
2010-01-06 7:49 ` Frans Meulenbroeks
2010-01-06 8:17 ` Koen Kooi
2010-01-06 15:26 ` Richard Purdie
2010-01-06 15:55 ` Martin Jansa
2010-01-06 22:09 ` Rolf Leggewie
2010-01-06 22:57 ` Philip Balister
2010-01-07 2:36 ` Holger Hans Peter Freyther
2010-01-07 7:59 ` Frans Meulenbroeks
2010-01-07 8:43 ` Graeme Gregory
2010-01-07 8:50 ` Frans Meulenbroeks
2010-01-07 9:21 ` Graeme Gregory
2010-01-07 9:35 ` Frans Meulenbroeks
2010-01-07 9:40 ` Koen Kooi [this message]
2010-01-07 9:54 ` Frans Meulenbroeks
2010-01-07 10:40 ` Rolf Leggewie
2010-01-07 11:01 ` Graeme Gregory
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='hi4a73$gpt$2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox