[oe] [PATCH 2/2] omap4430-panda: fix u-boot

Frans Meulenbroeks fransmeulenbroeks at gmail.com
Sat Jan 1 18:48:24 UTC 2011


2011/1/1 Philip Balister <philip at balister.org>:
> On 01/01/2011 01:12 PM, Frans Meulenbroeks wrote:
>>
>> We have a broken recipe and I feel it should be fixed.
>
> Broken only for some OE use cases. Not broken for others.
>
> The wrong solution to the problem is to replace a recipe that works for the
> people who use it with a recipe that creates untested output. U-boot is a
> fiddly piece of software, updates should be tested on hardware before they
> are pushed.
>
> Let's keep the focus on the real issue here, disappearing sources versus
> recipes that produce untested output.
>
> Disappearing sources are an issue beyond just rebased git repos. Distros
> that provide binaries to end users must provide for this event to provide
> GPL compliance. So it really is not a big deal.
>
> Philip
>

I am not going to rehash what I wrote a few minutes ago.

What I want to say is that there are other ways to fix the problem,
but the recipe maintainer does not care to fix the problem in a
generic way.

I'm well aware that u-boot is a complex thing
And I am more than happy to test the recipe as soon as my board
arrives. (actually I bumped into this issue as I was already preparing
the image I want to run on it).

Disappearing sources is indeed an issue. We saw that with
handhelds.org last month. Distro specific source archives, leading to
broken recipes for other distros is probably not the best solution.

One other thing:
I feel the way Koen is acting and the tone of his emails is not really
desirable for an open source project where several developers
cooperate to achieve a common goal.
Actually this kind of behaviour may well drive away people (e.g. to
Yocto). I am not too sure if that is desired.

Frans. (who wants to take this opportunity to wish everyone a good
2011 with lots of fun).




More information about the Openembedded-devel mailing list