[systemd-devel] Can apps ship their own copy of libudev?

[Koehne Kai]

Hi,

First time I post to the list, so please bear with me :) I'm a developer working on Qt. The Qt project just released a  beta of the upcoming version 5.2, and to help people to test it we've been also releasing an installer with binaries for Linux that is supposed to work on a variety of distributions. 

One of the problems [1] we still have to fix is our libudev.so.0 dependency ... That is, we're building the packages on Ubuntu 11.10 and link against system libudev.so.0 , while some modern distributions are (solely) providing libudev.so.1. For some parts of Qt the libudev dependency is actually not that important , and we can disable it. However, for the QtSerialPort library I've been told libudev is crucial: It uses it to enumerate all available ports.

So, to overcome this we've been thinking about building & shipping our own copy of libudev (renamed , or statically linked, to avoid clashes) ... Would you expect such a pristine version of libudev, compiled on distribution A , to work flawlessly on distribution B? What problems would you anticipate? 

Kind Regards

Kai Koehne

[1]: https://bugreports.qt-project.org/browse/QTBUG-34176

PS: Where can I vote for getting libudev into LSB ? :)

-- 
   Kai Köhne, Senior Software Engineer - Digia, Qt
   Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
   Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
   Sitz der Gesellschaft: Berlin. USt-IdNr: DE 286 306 868
   Registergericht: Amtsgericht Charlottenburg, HRB 144331 B