All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] babeltrace2: added 2.0.1
@ 2020-02-18 13:20 Anders Wallin
  2020-02-18 13:57 ` Alexander Kanavin
  0 siblings, 1 reply; 10+ messages in thread
From: Anders Wallin @ 2020-02-18 13:20 UTC (permalink / raw)
  To: openembedded-core

Babeltrace 1 vs. Babeltrace 2

The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was released.
Babeltrace 2 is a complete rewrite of the library, Python bindings, and CLI. It
is plugin based and offers much more features and potential than Babeltrace 1.

Because Babeltrace 2 is still a young released project, some distributions still
provide packages for the Babeltrace 1 project. Both projects can coexist on the
same system as there are no common installed files.

Signed-off-by: Anders Wallin <wallinux@gmail.com>
---
 .../recipes-kernel/lttng/babeltrace2_2.0.1.bb | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb

diff --git a/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
new file mode 100644
index 0000000000..d49a96faff
--- /dev/null
+++ b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
@@ -0,0 +1,26 @@
+SUMMARY = "Babeltrace2 - Trace Format Babel Tower"
+DESCRIPTION = "Babeltrace provides trace read and write libraries in host side, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readable log."
+HOMEPAGE = "http://babeltrace.org/"
+BUGTRACKER = "https://bugs.lttng.org/projects/babeltrace"
+LICENSE = "MIT & GPLv2 & LGPLv2.1 & BSD-2-Clause"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=a6a458c13f18385b7bc5069a6d7b176e"
+
+DEPENDS = "glib-2.0 util-linux popt bison-native flex-native"
+
+SRC_URI = "git://git.linuxfoundation.org/diamon/babeltrace.git;branch=stable-2.0"
+SRCREV = "06df58f89ee51b1a2c6a2c187ec3f15691633910"
+UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)$"
+
+S = "${WORKDIR}/git"
+
+inherit autotools pkgconfig
+
+EXTRA_OECONF = "--disable-debug-info"
+
+PACKAGECONFIG ??= "manpages"
+PACKAGECONFIG[manpages] = ", --disable-man-pages, asciidoc-native xmlto-native"
+
+FILES_${PN}-staticdev += "${libdir}/babeltrace2/plugins/*.a"
+FILES_${PN} += "${libdir}/babeltrace2/plugins/*.so"
+
+ASNEEDED = ""
-- 
2.25.0



^ permalink raw reply related	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-18 13:20 [PATCH] babeltrace2: added 2.0.1 Anders Wallin
@ 2020-02-18 13:57 ` Alexander Kanavin
  2020-02-19 10:06   ` Anders Wallin
  0 siblings, 1 reply; 10+ messages in thread
From: Alexander Kanavin @ 2020-02-18 13:57 UTC (permalink / raw)
  To: Anders Wallin; +Cc: OE-core

[-- Attachment #1: Type: text/plain, Size: 2774 bytes --]

Thanks. May I request that this recipe is named babletrace, while
babeltrace 1.x recipe is at the same time renamed to babeltrace1? I'd like
to avoid adding version numbers to the 'latest' version. Lttng should at
the same time be adjusted to use babeltrace1, as advised by upstream.

Alex

On Tue, 18 Feb 2020 at 14:21, Anders Wallin <wallinux@gmail.com> wrote:

> Babeltrace 1 vs. Babeltrace 2
>
> The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was
> released.
> Babeltrace 2 is a complete rewrite of the library, Python bindings, and
> CLI. It
> is plugin based and offers much more features and potential than
> Babeltrace 1.
>
> Because Babeltrace 2 is still a young released project, some distributions
> still
> provide packages for the Babeltrace 1 project. Both projects can coexist
> on the
> same system as there are no common installed files.
>
> Signed-off-by: Anders Wallin <wallinux@gmail.com>
> ---
>  .../recipes-kernel/lttng/babeltrace2_2.0.1.bb | 26 +++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100644 meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>
> diff --git a/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
> b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
> new file mode 100644
> index 0000000000..d49a96faff
> --- /dev/null
> +++ b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
> @@ -0,0 +1,26 @@
> +SUMMARY = "Babeltrace2 - Trace Format Babel Tower"
> +DESCRIPTION = "Babeltrace provides trace read and write libraries in host
> side, as well as a trace converter, which used to convert LTTng 2.0 traces
> into human-readable log."
> +HOMEPAGE = "http://babeltrace.org/"
> +BUGTRACKER = "https://bugs.lttng.org/projects/babeltrace"
> +LICENSE = "MIT & GPLv2 & LGPLv2.1 & BSD-2-Clause"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=a6a458c13f18385b7bc5069a6d7b176e"
> +
> +DEPENDS = "glib-2.0 util-linux popt bison-native flex-native"
> +
> +SRC_URI = "git://
> git.linuxfoundation.org/diamon/babeltrace.git;branch=stable-2.0"
> +SRCREV = "06df58f89ee51b1a2c6a2c187ec3f15691633910"
> +UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)$"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit autotools pkgconfig
> +
> +EXTRA_OECONF = "--disable-debug-info"
> +
> +PACKAGECONFIG ??= "manpages"
> +PACKAGECONFIG[manpages] = ", --disable-man-pages, asciidoc-native
> xmlto-native"
> +
> +FILES_${PN}-staticdev += "${libdir}/babeltrace2/plugins/*.a"
> +FILES_${PN} += "${libdir}/babeltrace2/plugins/*.so"
> +
> +ASNEEDED = ""
> --
> 2.25.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 4304 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-18 13:57 ` Alexander Kanavin
@ 2020-02-19 10:06   ` Anders Wallin
  2020-02-19 10:50     ` Alexander Kanavin
  2020-02-19 15:27     ` Jonathan Rajotte-Julien
  0 siblings, 2 replies; 10+ messages in thread
From: Anders Wallin @ 2020-02-19 10:06 UTC (permalink / raw)
  To: Alexander Kanavin, Jonathan Rajotte-Julien; +Cc: OE-core

[-- Attachment #1: Type: text/plain, Size: 3212 bytes --]

Hi Alex,

I think it's better to use babeltrace2 since it's a new version of
babeltrace.
The dist packages uses babeltrace2 and the main application/program is
called babeltrace2.

Jonatan; Do you have any comment on the naming?

Regards
Anders Wallin


On Tue, Feb 18, 2020 at 2:56 PM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> Thanks. May I request that this recipe is named babletrace, while
> babeltrace 1.x recipe is at the same time renamed to babeltrace1? I'd like
> to avoid adding version numbers to the 'latest' version. Lttng should at
> the same time be adjusted to use babeltrace1, as advised by upstream.
>
> Alex
>
> On Tue, 18 Feb 2020 at 14:21, Anders Wallin <wallinux@gmail.com> wrote:
>
>> Babeltrace 1 vs. Babeltrace 2
>>
>> The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was
>> released.
>> Babeltrace 2 is a complete rewrite of the library, Python bindings, and
>> CLI. It
>> is plugin based and offers much more features and potential than
>> Babeltrace 1.
>>
>> Because Babeltrace 2 is still a young released project, some
>> distributions still
>> provide packages for the Babeltrace 1 project. Both projects can coexist
>> on the
>> same system as there are no common installed files.
>>
>> Signed-off-by: Anders Wallin <wallinux@gmail.com>
>> ---
>>  .../recipes-kernel/lttng/babeltrace2_2.0.1.bb | 26 +++++++++++++++++++
>>  1 file changed, 26 insertions(+)
>>  create mode 100644 meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>>
>> diff --git a/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>> b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>> new file mode 100644
>> index 0000000000..d49a96faff
>> --- /dev/null
>> +++ b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>> @@ -0,0 +1,26 @@
>> +SUMMARY = "Babeltrace2 - Trace Format Babel Tower"
>> +DESCRIPTION = "Babeltrace provides trace read and write libraries in
>> host side, as well as a trace converter, which used to convert LTTng 2.0
>> traces into human-readable log."
>> +HOMEPAGE = "http://babeltrace.org/"
>> +BUGTRACKER = "https://bugs.lttng.org/projects/babeltrace"
>> +LICENSE = "MIT & GPLv2 & LGPLv2.1 & BSD-2-Clause"
>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=a6a458c13f18385b7bc5069a6d7b176e"
>> +
>> +DEPENDS = "glib-2.0 util-linux popt bison-native flex-native"
>> +
>> +SRC_URI = "git://
>> git.linuxfoundation.org/diamon/babeltrace.git;branch=stable-2.0"
>> +SRCREV = "06df58f89ee51b1a2c6a2c187ec3f15691633910"
>> +UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)$"
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +inherit autotools pkgconfig
>> +
>> +EXTRA_OECONF = "--disable-debug-info"
>> +
>> +PACKAGECONFIG ??= "manpages"
>> +PACKAGECONFIG[manpages] = ", --disable-man-pages, asciidoc-native
>> xmlto-native"
>> +
>> +FILES_${PN}-staticdev += "${libdir}/babeltrace2/plugins/*.a"
>> +FILES_${PN} += "${libdir}/babeltrace2/plugins/*.so"
>> +
>> +ASNEEDED = ""
>> --
>> 2.25.0
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>

[-- Attachment #2: Type: text/html, Size: 5088 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-19 10:06   ` Anders Wallin
@ 2020-02-19 10:50     ` Alexander Kanavin
  2020-02-19 15:27     ` Jonathan Rajotte-Julien
  1 sibling, 0 replies; 10+ messages in thread
From: Alexander Kanavin @ 2020-02-19 10:50 UTC (permalink / raw)
  To: Anders Wallin; +Cc: OE-core

[-- Attachment #1: Type: text/plain, Size: 3681 bytes --]

Basically I would like to maintain the principle that a recipe without a
version number is the 'latest' version, and staying on an older version has
to be an opt-in decision. There are already things like python3 and
gstreamer10 in core, and I would want to have less of that.

Alex

On Wed, 19 Feb 2020 at 11:06, Anders Wallin <wallinux@gmail.com> wrote:

> Hi Alex,
>
> I think it's better to use babeltrace2 since it's a new version of
> babeltrace.
> The dist packages uses babeltrace2 and the main application/program is
> called babeltrace2.
>
> Jonatan; Do you have any comment on the naming?
>
> Regards
> Anders Wallin
>
>
> On Tue, Feb 18, 2020 at 2:56 PM Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
>
>> Thanks. May I request that this recipe is named babletrace, while
>> babeltrace 1.x recipe is at the same time renamed to babeltrace1? I'd like
>> to avoid adding version numbers to the 'latest' version. Lttng should at
>> the same time be adjusted to use babeltrace1, as advised by upstream.
>>
>> Alex
>>
>> On Tue, 18 Feb 2020 at 14:21, Anders Wallin <wallinux@gmail.com> wrote:
>>
>>> Babeltrace 1 vs. Babeltrace 2
>>>
>>> The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was
>>> released.
>>> Babeltrace 2 is a complete rewrite of the library, Python bindings, and
>>> CLI. It
>>> is plugin based and offers much more features and potential than
>>> Babeltrace 1.
>>>
>>> Because Babeltrace 2 is still a young released project, some
>>> distributions still
>>> provide packages for the Babeltrace 1 project. Both projects can coexist
>>> on the
>>> same system as there are no common installed files.
>>>
>>> Signed-off-by: Anders Wallin <wallinux@gmail.com>
>>> ---
>>>  .../recipes-kernel/lttng/babeltrace2_2.0.1.bb | 26 +++++++++++++++++++
>>>  1 file changed, 26 insertions(+)
>>>  create mode 100644 meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>>>
>>> diff --git a/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>>> b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>>> new file mode 100644
>>> index 0000000000..d49a96faff
>>> --- /dev/null
>>> +++ b/meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb
>>> @@ -0,0 +1,26 @@
>>> +SUMMARY = "Babeltrace2 - Trace Format Babel Tower"
>>> +DESCRIPTION = "Babeltrace provides trace read and write libraries in
>>> host side, as well as a trace converter, which used to convert LTTng 2.0
>>> traces into human-readable log."
>>> +HOMEPAGE = "http://babeltrace.org/"
>>> +BUGTRACKER = "https://bugs.lttng.org/projects/babeltrace"
>>> +LICENSE = "MIT & GPLv2 & LGPLv2.1 & BSD-2-Clause"
>>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=a6a458c13f18385b7bc5069a6d7b176e"
>>> +
>>> +DEPENDS = "glib-2.0 util-linux popt bison-native flex-native"
>>> +
>>> +SRC_URI = "git://
>>> git.linuxfoundation.org/diamon/babeltrace.git;branch=stable-2.0"
>>> +SRCREV = "06df58f89ee51b1a2c6a2c187ec3f15691633910"
>>> +UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)$"
>>> +
>>> +S = "${WORKDIR}/git"
>>> +
>>> +inherit autotools pkgconfig
>>> +
>>> +EXTRA_OECONF = "--disable-debug-info"
>>> +
>>> +PACKAGECONFIG ??= "manpages"
>>> +PACKAGECONFIG[manpages] = ", --disable-man-pages, asciidoc-native
>>> xmlto-native"
>>> +
>>> +FILES_${PN}-staticdev += "${libdir}/babeltrace2/plugins/*.a"
>>> +FILES_${PN} += "${libdir}/babeltrace2/plugins/*.so"
>>> +
>>> +ASNEEDED = ""
>>> --
>>> 2.25.0
>>>
>>> --
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>

[-- Attachment #2: Type: text/html, Size: 5848 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-19 10:06   ` Anders Wallin
  2020-02-19 10:50     ` Alexander Kanavin
@ 2020-02-19 15:27     ` Jonathan Rajotte-Julien
  2020-02-19 15:38       ` Richard Purdie
  1 sibling, 1 reply; 10+ messages in thread
From: Jonathan Rajotte-Julien @ 2020-02-19 15:27 UTC (permalink / raw)
  To: Anders Wallin; +Cc: OE-core

On Wed, Feb 19, 2020 at 11:06:12AM +0100, Anders Wallin wrote:
> Hi Alex,
> 
> I think it's better to use babeltrace2 since it's a new version of
> babeltrace.
> The dist packages uses babeltrace2 and the main application/program is
> called babeltrace2.
> 
> Jonatan; Do you have any comment on the naming?

Me?

Don't care much about the naming. The major issue here is the dependency for
ptest of lttng-tools that depends on a "babeltrace" executable and not on the
"babeltrace2" executable. Currently on our CI we create a symlink from
"babeltrace2" to "babeltrace". This is something we plan on addressing shortly.

Cheers



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-19 15:27     ` Jonathan Rajotte-Julien
@ 2020-02-19 15:38       ` Richard Purdie
  2020-02-19 15:56         ` Jonathan Rajotte-Julien
  0 siblings, 1 reply; 10+ messages in thread
From: Richard Purdie @ 2020-02-19 15:38 UTC (permalink / raw)
  To: Jonathan Rajotte-Julien, Anders Wallin; +Cc: OE-core

On Wed, 2020-02-19 at 10:27 -0500, Jonathan Rajotte-Julien wrote:
> On Wed, Feb 19, 2020 at 11:06:12AM +0100, Anders Wallin wrote:
> > Hi Alex,
> > 
> > I think it's better to use babeltrace2 since it's a new version of
> > babeltrace.
> > The dist packages uses babeltrace2 and the main application/program
> > is
> > called babeltrace2.
> > 
> > Jonatan; Do you have any comment on the naming?
> 
> Me?
> 
> Don't care much about the naming. The major issue here is the
> dependency for
> ptest of lttng-tools that depends on a "babeltrace" executable and
> not on the
> "babeltrace2" executable. Currently on our CI we create a symlink
> from
> "babeltrace2" to "babeltrace". This is something we plan on
> addressing shortly.

Let me try a different question. What is the ultimate intent here?

Will babeltrace and babeltrace2 coexist in the future or do you plan to
rename babeltrace2 -> babeltrace at some point?

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.

Cheers,

Richard



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-19 15:38       ` Richard Purdie
@ 2020-02-19 15:56         ` Jonathan Rajotte-Julien
  2020-02-19 16:02           ` Alexander Kanavin
  0 siblings, 1 reply; 10+ messages in thread
From: Jonathan Rajotte-Julien @ 2020-02-19 15:56 UTC (permalink / raw)
  To: Richard Purdie; +Cc: OE-core

> Let me try a different question. What is the ultimate intent here?
> 
> Will babeltrace and babeltrace2 coexist in the future or do you plan to
> rename babeltrace2 -> babeltrace at some point?

We plan on deprecating Babeltrace 1.X in the long term but Babeltrace 2 and
Babeltrace 1 will always co-exist.

> 
> 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.

-- 
Jonathan Rajotte-Julien
EfficiOS


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-19 15:56         ` Jonathan Rajotte-Julien
@ 2020-02-19 16:02           ` Alexander Kanavin
  2020-02-20 12:38             ` Anders Wallin
  0 siblings, 1 reply; 10+ messages in thread
From: Alexander Kanavin @ 2020-02-19 16:02 UTC (permalink / raw)
  To: Jonathan Rajotte-Julien; +Cc: OE-core

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

On Wed, 19 Feb 2020 at 16:56, Jonathan Rajotte-Julien <
jonathan.rajotte-julien@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

[-- Attachment #2: Type: text/html, Size: 1027 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-19 16:02           ` Alexander Kanavin
@ 2020-02-20 12:38             ` Anders Wallin
  2020-02-20 12:42               ` Alexander Kanavin
  0 siblings, 1 reply; 10+ messages in thread
From: Anders Wallin @ 2020-02-20 12:38 UTC (permalink / raw)
  To: Alexander Kanavin; +Cc: OE-core

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

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@gmail.com>
wrote:

> On Wed, 19 Feb 2020 at 16:56, Jonathan Rajotte-Julien <
> jonathan.rajotte-julien@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@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 2099 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH] babeltrace2: added 2.0.1
  2020-02-20 12:38             ` Anders Wallin
@ 2020-02-20 12:42               ` Alexander Kanavin
  0 siblings, 0 replies; 10+ messages in thread
From: Alexander Kanavin @ 2020-02-20 12:42 UTC (permalink / raw)
  To: Anders Wallin; +Cc: OE-core

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

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@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@gmail.com>
> wrote:
>
>> On Wed, 19 Feb 2020 at 16:56, Jonathan Rajotte-Julien <
>> jonathan.rajotte-julien@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@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>

[-- Attachment #2: Type: text/html, Size: 2867 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2020-02-20 12:42 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-18 13:20 [PATCH] babeltrace2: added 2.0.1 Anders Wallin
2020-02-18 13:57 ` Alexander Kanavin
2020-02-19 10:06   ` Anders Wallin
2020-02-19 10:50     ` Alexander Kanavin
2020-02-19 15:27     ` Jonathan Rajotte-Julien
2020-02-19 15:38       ` Richard Purdie
2020-02-19 15:56         ` Jonathan Rajotte-Julien
2020-02-19 16:02           ` Alexander Kanavin
2020-02-20 12:38             ` Anders Wallin
2020-02-20 12:42               ` Alexander Kanavin

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.