<div dir="ltr">Generally this should be done by the person introducing the new recipe.<div><br></div><div>Also check that upstream version check works correctly for both:</div><div>devtool latest-version babeltrace (this should be probably limited to 1.x versions)</div><div>devtool latest-version babeltrace2</div><div><br></div><div>Alex</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 20 Feb 2020 at 13:39, Anders Wallin <<a href="mailto:wallinux@gmail.com">wallinux@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Alex,<div><br></div><div>should I update the patch to include changes to maintainer file, packagegroup etc in the same way as for babeltrace or </div><div>is it something you will do? </div><div><br></div><div><div><div dir="ltr">Anders Wallin</div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 19, 2020 at 5:02 PM Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Wed, 19 Feb 2020 at 16:56, Jonathan Rajotte-Julien <<a href="mailto:jonathan.rajotte-julien@efficios.com" target="_blank">jonathan.rajotte-julien@efficios.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">> There are some things where the namespaces are quite specific (python<br>
> vs python3, gtk(+) 2/3/4, qt) but they're fairly few and far between.<br>
> <br>
> If babeltrace2 will replace babeltrace and become babeltrace, we<br>
> probably want to keep PN as babeltrace. If it will be known as<br>
> babeltrace2 always, we probably change PN.<br>
<br>
Babeltrace 2 executable will be forever named babeltrace2.<br>
<br>
Hope this clear up this part a bit.<br></blockquote><div><br></div><div>Right, then I'm fine with naming the recipe babeltrace2.</div><div><br></div><div>Alex </div></div></div>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div>
</blockquote></div>