Bryan Kadzban wrote: > Bruce Dubbs wrote: >> LIBUDEV_MAJOR = .1 >> LIBUDEV_MINOR = .0 >> LIBUDEV_PATCH = .2 > > Note that (if upstream does this correctly) these will change with every > change to libudev. Not sure if there's some way to pull the values from > their Makefile.am (probably not terribly easy), or otherwise figure it > out automatically?
Makefile.am has LIBUDEV_CURRENT=1 LIBUDEV_REVISION=2 LIBUDEV_AGE=0 This only changes if the library interface changes. If they only add something new, then REVISION changes. I don't know what circumstances would change 'AGE'. > I don't know how often we'll have to change these, so maybe it'll be OK > as is. But note that LIBUDEV_MAJOR matters for binary-incompatible code > changes, so we will need to get it right if it ever changes again. And I > have a libudev.so.0 symlink on this machine, so it has changed in the > past at some point. In that case, I suspect they did something to change the behavior of the library that causes a conflict between .0 and .1. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
