babeltrace2: added 2.0.1
PATCH 1/1 babeltrace2: added 2.0.1
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.
--- .../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
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +26 -0
@@ -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 = ""
Signature · 1 line
2.25.0
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
Quoted 67 lines · Anders Wallin
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 <[email protected]>--- .../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.bbmeta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +2
-0@@ -0,0 +1,26 @@ +SUMMARY = "Babeltrace2 - Trace Format Babel Tower" +DESCRIPTION = "Babeltrace provides trace read and write libraries in hostside, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readable log."
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +8
-0+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"
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +11
-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-nativexmlto-native"
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +5
-1+ +FILES_${PN}-staticdev += "${libdir}/babeltrace2/plugins/*.a" +FILES_${PN} += "${libdir}/babeltrace2/plugins/*.so" + +ASNEEDED = "" --2.25.0
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
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
Quoted 77 lines · Alexander Kanavin
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
Quoted 67 lines · Anders Wallin
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 <[email protected]>--- .../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.bbmeta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +2
-0@@ -0,0 +1,26 @@ +SUMMARY = "Babeltrace2 - Trace Format Babel Tower" +DESCRIPTION = "Babeltrace provides trace read and write libraries inhost side, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readable log."
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +8
-0+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"
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +11
-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-nativexmlto-native"
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +5
-1+ +FILES_${PN}-staticdev += "${libdir}/babeltrace2/plugins/*.a" +FILES_${PN} += "${libdir}/babeltrace2/plugins/*.so" + +ASNEEDED = "" --2.25.0
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
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
Quoted 93 lines · Anders Wallin
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 WallinQuoted 77 lines · Alexander Kanavin
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
Quoted 67 lines · Anders Wallin
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 <[email protected]>--- .../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.bbmeta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +2
-0@@ -0,0 +1,26 @@ +SUMMARY = "Babeltrace2 - Trace Format Babel Tower" +DESCRIPTION = "Babeltrace provides trace read and write libraries inhost side, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readable log."
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +8
-0+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"
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +11
-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-nativexmlto-native"
meta/recipes-kernel/lttng/babeltrace2_2.0.1.bb new file +5
-1+ +FILES_${PN}-staticdev += "${libdir}/babeltrace2/plugins/*.a" +FILES_${PN} += "${libdir}/babeltrace2/plugins/*.so" + +ASNEEDED = "" --2.25.0
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 8 lines · Anders Wallin
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
Quoted 13 lines · Jonathan Rajotte-Julien
Quoted 9 lines · Anders Wallin
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?
Quoted 8 lines
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
Quoted 4 lines
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.
Quoted 7 lines
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.
Signature · 2 lines
Jonathan Rajotte-Julien EfficiOS
Quoted 11 lines · Jonathan Rajotte-Julien
Quoted 6 lines
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
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
Quoted 24 lines · Alexander Kanavin
Quoted 11 lines · Jonathan Rajotte-Julien
Quoted 6 lines
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
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
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
Quoted 37 lines · Anders Wallin
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
Quoted 24 lines · Alexander Kanavin
Quoted 11 lines · Jonathan Rajotte-Julien
Quoted 6 lines
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
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core