Re: [RFC] Packaging libtraceevent.so

From: Steven Rostedt
Date: Tue Dec 03 2013 - 10:23:27 EST


On Tue, 3 Dec 2013 08:56:33 -0500
Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote:


> So the level of stable I think would be needed is basically being able
> to ship a new libtraceevent.so and have it not break a powertop that
> was linked against a previous version. E.g. libtraceevent.so provided
> with the 3.15 kernel release can be used as an update to the
> libtraceevent.so from the 3.13 release and powertop doesn't need to be
> rebuilt.
>
> That's typically done with soname and/or symbol versioning. Clearly
> applications wishing to use new libtraceevent features would need to
> be rebuilt to take advantage of those, but basic functionality should
> be pretty stable. Changing soname/ABI happens elsewhere in userspace
> libs and isn't a big deal for development, but those bumps typically
> aren't done in the middle of a released distro version. There are
> several distros that do major kernel version updates during the
> lifetime of a release so anything coming from those needs to be
> handled carefully.

There's a couple of things that need to be cleaned up first, that will
affect current users. But they are minor. I think we can work on this
soon and get something out by the next release.

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/