<br><br><div class="gmail_quote">2011/10/20 Koen Kooi <span dir="ltr"><<a href="mailto:koen@dominion.thruhere.net">koen@dominion.thruhere.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Op 20 okt. 2011, om 13:21 heeft Richard Purdie het volgende geschreven:<br>
<div><div></div><div class="h5"><br>
> On Thu, 2011-10-20 at 08:23 +0200, Koen Kooi wrote:<br>
>> Op 28 sep. 2011, om 22:04 heeft Otavio Salvador het volgende geschreven:<br>
>><br>
>>> On Wed, Sep 28, 2011 at 16:50, Richard Purdie<br>
>>> <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br>
>>>>> This patch improves the current situation and I don't foresee the<br>
>>>>> autoPR code working soon<br>
>>>><br>
>>>> Which is why we need to switch to that model and shake out the issues<br>
>>>> sooner than later. Enough is enough with the PR madness and we need to<br>
>>>> get to grips and fix it.<br>
>>><br>
>>> I fully agree this is the way to go but this doesn't mean we ought to<br>
>>> hold this patch until all this happens. This patch allows the removal<br>
>>> of the kernel.bbclass from meta-oe so reducing the delta between<br>
>>> oe-core and meta-oe.<br>
>><br>
>> So a month later and no sign of the mythical working<br>
>> auto-PR-incrementer or work on it.<br>
><br>
> A month where we were stabilising for a release. Its on the 1.2 feature<br>
> list and as it happens I've been hearing questions about what is needed<br>
> here.<br>
><br>
>> So can this patch go in? It would mean we can drop kernel.bbclass<br>
>> from meta-oe.<br>
><br>
> I *HATE* this PR bumping stuff. I've just been told we likely need to<br>
> bump the PR for anything using libGL which once again shows that build<br>
> system basically failing to automate building things.<br>
><br>
> So I'm drawing a line here and no, we can't take this. If its fine to<br>
> expect people to bump PR values manually for lib* changes, its fine for<br>
> kernels too. I'd suggest you do drop this from meta-oe and we start<br>
> building up pressure for the problem to get fixed properly rather than<br>
> letting people wallpaper over the cracks.<br>
<br>
</div></div>I have products to ship, so treating meta-oe as a plaything and break this for the sake of breaking it is unacceptable. I'll let oe-core have the monopoly on high-qualitily, but broken metadata.<br>
<div><div></div><div>.<br></div></div></blockquote><div><br>Didn't we have a TSC to escalate discussions and disagreements between developers to???<br><br>Best regards, Frans<br></div></div>