public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Josh Boyer <jwboyer@fedoraproject.org>,
	Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [RFC] Packaging libtraceevent.so
Date: Mon, 02 Dec 2013 11:04:25 -0800	[thread overview]
Message-ID: <529CD9B9.7060003@linux.intel.com> (raw)
In-Reply-To: <20131202140322.4ad6a151@gandalf.local.home>

On 12/2/2013 11:03 AM, Steven Rostedt wrote:
> Hi all!
>
> The question has recently come up in Fedora about packaging the
> libtraceevent.so library. Currently there's 4 users of it:
>
>   1) perf
>   2) trace-cmd
>   3) powertop
>   4) rasdaemon
>
> But each have their own copy of the code.
>
> Both perf and trace-cmd are the major developers of the package, and I
> would recommend that they continue using the *.a version, but for those
> tools that are simple users of the library, it would probably make
> sense to have them use libtraceevent.so and remove their copies from
> the code (powertop and rasdaemon).
>
> The question that I'm posing here is, what currently needs to be done
> to have this happen?
>
> Is the API stable enough for a release?
>
> We probably should have a dot versioning with the .so (ie.
> libtraceevent.so.1)
>
> So what are people's thoughts on this topic?
>

powertop would much rather use a system copy than our own...
but if it's not there in common distros we need to carry our own obviously


  reply	other threads:[~2013-12-02 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 19:03 [RFC] Packaging libtraceevent.so Steven Rostedt
2013-12-02 19:04 ` Arjan van de Ven [this message]
2013-12-03  6:02 ` Namhyung Kim
2013-12-03 13:56   ` Josh Boyer
2013-12-03 15:23     ` Steven Rostedt
2013-12-03 15:22   ` Steven Rostedt

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=529CD9B9.7060003@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.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