From: Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] babeltrace: update to 1.5.8
Date: Mon, 17 Feb 2020 11:48:18 -0500 [thread overview]
Message-ID: <20200217164818.GC17818@joraj-alpa> (raw)
In-Reply-To: <CANNYZj-nk-txm1rUGd8ABY10ZQ=DkMEA0CexQsMDinuQxaTmkA@mail.gmail.com>
Hi,
On Mon, Feb 17, 2020 at 12:43:43PM +0100, Alexander Kanavin wrote:
> Also, there’s now a babeltrace 2, so we should update to that rather ?
Babeltrace 1.5.x and Babeltrace 2 are "setup" to be co-installed.
Currently lttng-tools depends on babeltrace 1.5 for testing (the "babeltrace"
excutable). We plan to make the switch officialy in the upcoming months.
We recommend (upstream) that if a Babeltrace2 recipe is to be exposed that it is
done so in parallel to a Babeltrace 1.5.x recipe and that the default be
Babeltrace 1.5.x for now. AFAIK all tests from lttng-tools do pass when using
Babeltrace2 and babeltrace2 is full compatible (CLI) with babeltrace 1.5.x.
Still, we recommended that for now 1.5.x be the default.
Cheers
>
> Alex
>
> On Mon 17. Feb 2020 at 12.03, Jacob Kroon <jacob.kroon@gmail.com> wrote:
>
> > On 2/17/20 11:59 AM, Anders Wallin wrote:
> > > updated HOMEPAGE to http://babeltrace.org/
> > > updated LICENSE to include LGPLv2.1
> > >
> > > Signed-off-by: Anders Wallin <wallinux@gmail.com>
> > > ---
> > > meta/recipes-kernel/lttng/babeltrace_1.5.8.bb | 20 +++++++++++++++++++
> > > 1 file changed, 20 insertions(+)
> > > create mode 100644 meta/recipes-kernel/lttng/babeltrace_1.5.8.bb
> > >
> > > diff --git a/meta/recipes-kernel/lttng/babeltrace_1.5.8.bb
> > b/meta/recipes-kernel/lttng/babeltrace_1.5.8.bb
> > > new file mode 100644
> > > index 0000000000..b6b7653037
> > > --- /dev/null
> > > +++ b/meta/recipes-kernel/lttng/babeltrace_1.5.8.bb
> > > @@ -0,0 +1,20 @@
> > > +SUMMARY = "Babeltrace - 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"
> > > +LIC_FILES_CHKSUM = "file://LICENSE;md5=76ba15dd76a248e1dd526bca0e2125fa"
> > > +
> > > +DEPENDS = "glib-2.0 util-linux popt bison-native flex-native"
> > > +
> > > +SRC_URI = "git://
> > git.linuxfoundation.org/diamon/babeltrace.git;branch=stable-1.5"
> > > +SRCREV = "054a54ae10b01a271afc4f19496c041b10fb414c"
> > > +UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)$"
> > > +
> > > +S = "${WORKDIR}/git"
> > > +
> > > +inherit autotools pkgconfig
> > > +
> > > +EXTRA_OECONF = "--disable-debug-info"
> > > +
> > > +ASNEEDED = ""
> > >
> >
> > Looks like this patch adds a new recipe for 1.5.8, and keeps the 1.5.7
> > recipe. Was that intentional ?
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Jonathan Rajotte-Julien
EfficiOS
next prev parent reply other threads:[~2020-02-17 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 10:59 [PATCH] babeltrace: update to 1.5.8 Anders Wallin
2020-02-17 11:03 ` Jacob Kroon
2020-02-17 11:43 ` Alexander Kanavin
2020-02-17 16:48 ` Jonathan Rajotte-Julien [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-17 13:32 Anders Wallin
2020-02-17 15:38 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200217164818.GC17818@joraj-alpa \
--to=jonathan.rajotte-julien@efficios.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox