[OE-core] [PATCH] [PATCH] raptor: add recipe

[Ben Gardiner]

On Thu, Jul 28, 2011 at 10:46 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>
> Op 28 jul. 2011, om 16:43 heeft Ben Gardiner het volgende geschreven:
>
>> Hi Koen,
>>
>> On Thu, Jul 28, 2011 at 10:36 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>>>
>>> Op 28 jul. 2011, om 16:29 heeft Ben Gardiner het volgende geschreven:
>>>
>>>> On Thu, Jul 28, 2011 at 10:24 AM, Frans Meulenbroeks
>>>> <fransmeulenbroeks at gmail.com> wrote:
>>>>>
>>>>>
>>>>> 2011/7/28 Ben Gardiner <bengardiner at nanometrics.ca>
>>>>>>
>>>>>>
>>>>>> Well, I would not submit _this_ patch for pull-request. I was hoping
>>>>>> to get this version of raptor included and then submit a pull-request
>>>>>> for a cherry-pick of the patch to add libxml2 to DEPENDS.
>>>>>
>>>>> Ah, missed that you also added libxml2.
>>>>> Not sure about the policies of the maintenance branch, but I suspect the
>>>>> proper way would be to fix and test in openembedded then submit a pull
>>>>> request.
>>>>> Then again maybe the policies for the maintenance branch are different.
>>>>
>>>> :) They are. AFAICT I need to get this recipe (including libxml2 dep
>>>> update) into oe-core or its layers :)
>>>
>>> I ask again, what makes you think that? Pretty much all of the recent maintenance commits are from .dev.
>>
>> I'm sorry I guess my previous reply got lost in the noise. I think
>> that because I read it from Tom. If it is at all possible to
>> circumvent this requirement
>
> What did you exactly read and why do you think it's a requirement? From http://wiki.openembedded.org/index.php/2011.03-maintenance:
>
> "Changes may reside in either the openembedded 'master' repository OR a relevant public layer in the oe-core / meta-oe / etc universe"

I read:

In Message-ID: <4DFA7108.5020103 at mentor.com> On Thu, Jun 16, 2011 at
5:09 PM, Tom Rini <tom_rini at mentor.com> wrote:
> [...]
> the policy about where changes need to be before they can be included in
> 2011.03-maintenance to include being in oe-core / meta-oe or other
> relevant public layer instead of being only in the oe.dev master branch.

and took "instead of being only" to mean that the development effort
must shift to pushing into oe-core (or it's layers).

My mistake and thank you for clarifying this is not a requirement.
Please drop this patch from consideration.

Best Regards,
Ben Gardiner

---
Nanometrics Inc.
http://www.nanometrics.ca