[meta-virtualization] [PATCH 1/3] protobuf: uprev 3.0.0 from 2.6.1

[Bruce Ashfield]

On Wed, Sep 7, 2016 at 6:05 AM, Jack Mitchell <ml at embed.me.uk> wrote:

>
> On 07/09/16 09:09, jianchuan.wang at windriver.com wrote:
>
>> From: Jianchuan Wang <jianchuan.wang at windriver.com>
>>
>> Signed-off-by: Jianchuan Wang <jianchuan.wang at windriver.com>
>> ---
>>  .../criu/protobuf-native_2.6.1.bb                  | 21 -----
>>  .../criu/protobuf-native_3.0.0.bb                  | 21 +++++
>>  .../recipes-containers/criu/protobuf_2.6.1.bb      | 97
>> ----------------------
>>  .../recipes-containers/criu/protobuf_3.0.0.bb      | 97
>> ++++++++++++++++++++++
>>  4 files changed, 118 insertions(+), 118 deletions(-)
>>  delete mode 100644 meta-virtualization/recipes-containers/criu/
>> protobuf-native_2.6.1.bb
>>  create mode 100644 meta-virtualization/recipes-containers/criu/
>> protobuf-native_3.0.0.bb
>>  delete mode 100644 meta-virtualization/recipes-containers/criu/
>> protobuf_2.6.1.bb
>>  create mode 100644 meta-virtualization/recipes-containers/criu/
>> protobuf_3.0.0.bb
>>
>> >
> > <snip>
>
> Is there a reason not to use and update the version is meta-oe? Why the
> duplication?


See the meta-oe mailing list, where I discussed this not that long ago.

Up until now, I haven't been able to have stability or a fast patch merge
process into
the meta-go* or oe-meta-go layers.

I do builds with them from time to time .. after a period of stability,
I'll drop support
in favour of them .. but until that time, we keep our copies.

Bruce


>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-virtualization/attachments/20160907/17b47d43/attachment.html>