[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131202140322.4ad6a151@gandalf.local.home>
Date: Mon, 2 Dec 2013 14:03:22 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: LKML <linux-kernel@...r.kernel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Josh Boyer <jwboyer@...oraproject.org>,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
Arjan van de Ven <arjan@...ux.intel.com>
Subject: [RFC] Packaging libtraceevent.so
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?
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists