Re: why we don't setup a buildbot for openembedded QA?

[Holger Hans Peter Freyther <holger+oe@freyther.de>]

On Thursday 07 January 2010 03:02:05 Guo Hongruan wrote:
> 在 Wed, 06 Jan 2010 11:59:45 +0800，Holger Hans Peter Freyther

> 
> Yes, I agree with you. It is not worth to make sure every combinations of
> GCC, GLIBC and BINUTILS work perfectly. For example, some versions of
> binutils is too old to work with newest glibc/gcc and there are little
> projects using these combinations.
> 
> But, My idea is that we can maintain a table which records which version
> of package A can not work with which version of package B.
> (for example, glibc-2.6.1 can not work with binutils-2.20)
> So that, when the user chooses these combinations, the
> openembedded/bitbake can give them a warning or error to indicate that
> this combination will not work.

Well, the Angstrom, Minimal, Micro are these documentations. People sat down 
and tested the configurations and then used it. I believe it is more valuable 
to document what is working and in the mainstream than to document which 
exotic configurations do not work (think of the cross-tool picture where 
everything is red)

OpenEmbedded is a tool for power users, if they really need to use a specific 
version of glibc they should be able to deal with the errors and resolve them.


I pointed out some areas where OE is really lacking in QA and it would be cool 
if you would be interested in that as well.