[OE-core] [PATCH] babeltrace2: added 2.0.1

Alexander Kanavin alex.kanavin at gmail.com
Thu Feb 20 12:42:26 UTC 2020


Generally this should be done by the person introducing the new recipe.

Also check that upstream version check works correctly for both:
devtool latest-version babeltrace (this should be probably limited to 1.x
versions)
devtool latest-version babeltrace2

Alex

On Thu, 20 Feb 2020 at 13:39, Anders Wallin <wallinux at gmail.com> wrote:

> Hi Alex,
>
> should I update the patch to include changes to maintainer file,
> packagegroup etc in the same way as for babeltrace or
> is it something you will do?
>
> Anders Wallin
>
>
> On Wed, Feb 19, 2020 at 5:02 PM Alexander Kanavin <alex.kanavin at gmail.com>
> wrote:
>
>> On Wed, 19 Feb 2020 at 16:56, Jonathan Rajotte-Julien <
>> jonathan.rajotte-julien at efficios.com> wrote:
>>
>>> > There are some things where the namespaces are quite specific (python
>>> > vs python3, gtk(+) 2/3/4, qt) but they're fairly few and far between.
>>> >
>>> > If babeltrace2 will replace babeltrace and become babeltrace, we
>>> > probably want to keep PN as babeltrace. If it will be known as
>>> > babeltrace2 always, we probably change PN.
>>>
>>> Babeltrace 2 executable will be forever named babeltrace2.
>>>
>>> Hope this clear up this part a bit.
>>>
>>
>> Right, then I'm fine with naming the recipe babeltrace2.
>>
>> Alex
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20200220/12da72c6/attachment.html>


More information about the Openembedded-core mailing list