From: Tony Jones <tonyj@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>,
Patrick McLean <patrick.mclean@sony.com>,
John Kacur <jkacur@redhat.com>,
Alan Mikhak <amikhak@wirelessfabric.com>,
Seth Forshee <seth.forshee@canonical.com>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Nivedita Swaminathan <nivedita.swaminathan@intel.com>
Subject: Re: Getting libtraceevent into a packaged library
Date: Thu, 3 Oct 2019 12:22:57 -0700 [thread overview]
Message-ID: <8f89cd24-a054-9ec9-6844-ad7ffb513677@suse.de> (raw)
In-Reply-To: <20191003150104.74216a0a@gandalf.local.home>
On 10/3/19 12:01 PM, Steven Rostedt wrote:
> My question is now, how to we go about having distributions package it.
> Like perf, the main source code lives in the Linux kernel source tree
> under:
>
> tools/lib/traceevent
We're happy to look into this.
> What's the next step to get this into a package so that perf,
> trace-cmd, power-top, rasdaemon, uftrace, and whatever does not need to
> have its own copy of the code, but instead link to it.
If building perf from source (git) it would be useful to be able to select either the lib/traceevent in the tree (probably
should be the default) or the libtraceevent installed via rpm/etc. Obviously the later is a pre-requisite to being able
to package perf with a rpm build-requires on the libtraceevent-devel rpm.
> Let me know of anyone else that can help in getting this packaged for a
> Linux distribution.
Tony
next prev parent reply other threads:[~2019-10-03 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 19:01 Getting libtraceevent into a packaged library Steven Rostedt
2019-10-03 19:22 ` Tony Jones [this message]
2019-10-04 2:51 ` Namhyung Kim
2019-10-04 13:33 ` Steven Rostedt
2019-10-06 14:15 ` Namhyung Kim
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=8f89cd24-a054-9ec9-6844-ad7ffb513677@suse.de \
--to=tonyj@suse.de \
--cc=amikhak@wirelessfabric.com \
--cc=jkacur@redhat.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=namhyung@kernel.org \
--cc=nivedita.swaminathan@intel.com \
--cc=patrick.mclean@sony.com \
--cc=rostedt@goodmis.org \
--cc=seth.forshee@canonical.com \
/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;
as well as URLs for NNTP newsgroup(s).