Re: libudev major number not increased

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 14, 2009 at 15:47, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
>> > The _major_ number of libudev has to be increased, because several symbols
>> > were removed (e.g. udev_device_new_from_devpath()) from the library in the
>> > changes from 128 to 129.
>> >
>> > Which means, that every application, which linked to a udev version prior to
>> > udev-129 has to be recompiled to work with newer libudev versions and
>> > unfortunately there is now no way to install compat libs anymore.
>>
>> Right, we do not bump the major number as long as it is experimental.
>>
>> It's not only the API which has changed in earlier versions, also the
>> logic behind it, so it would not really work with compat libs anyway.
>> The usual way to do compat libs by taking the code from old packages
>> will also not work, because the lib is tied to the running udev
>> version. Older libs are unlikely to work with a new udev running.
>
> you don't need to bump the package version number. Just bump the .so
> name/version of the library.

Yeah, but we have the Debian-like lib packaging with the package name
following the lib version. The build system will not allow to have
different versions.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux