[oe] What to do about the poor bitbake Quality Control?

[Philip Balister]

On 08/14/2010 12:01 PM, Frans Meulenbroeks wrote:
> 2010/8/14 AJ ONeal<coolaj86 at gmail.com>:
>> This is about the 4th time that I've `rm -rf`-d everything and started from
>> scratch and never yet got a working `bitbake omap3-console-image`
>>
>> Every time I `git pull` it's a different set of problems. It's never the
>> same package twice, but they never all compile for the basic console image
>> anywhere from 4 to 20 hours in.
>>
>> Fortunately, I do have a machine that did build omap3-console-image a few
>> weeks ago at work. But I've never been able to get it on my machine at home
>> (same os) to start playing around with.
>>
>> What needs to happen in order for things to git checked that they work with
>> at least a few common meta-tasks before being pushed out?
>> And is there anything I can do to help? (Donate some machine time to run
>> tests, for example)
>>
>>
>> Obviously, we all have our day jobs and whatnot, but this is becoming really
>> frustrating for me and I'd like to see things improve.
>>
>
> If you are using dev head, you're living on the edge. If you can't
> stand that better use the stable branch.
>
> As far as there are issues:
> Either report them, or better fix them.
> (or as a workaround you could find the commit wthat broke it and
> report that and perhaps temporariy locally revert that commit if you
> cannot fix it).
>
> Having said that:
> I don't really see many issues. Maybe I'm building a different set of
> packages or for a different set of hw or for a different distro.

I think they are building from the gumstix overo repo. We are interested 
in failures (at least failures for recipes that are in .dev), but we 
can't guarantee when our fixes will hit the gumstix repository.

Philip

Philip