On Sun, Feb 22, 2009 at 2:16 PM, Chris Bagwell <chris at cnpbagwell.com> wrote:
> Hmm, I did notice one interesting thing. I went ahead and re-installed > sane-1.0.19 back on top of the pre-existing private directory that had both > 1.0.19 and 1.1.0-cvs installed. > > sane-1.0.19's libtool did overwrite all symlinks (based on timestamps) but > chose different values at different levels. That's weird, but not surprising. We've had quite alot of bitrot in the build system until you showed up :) > Re-installing CVS points *everything* back to 1.1.0 so. Yes- i can confirm that it works as expected on top of a vendor-packaged 1.0.19, except for one problem: /usr/lib/sane/libsane.so.1 -> libsane-xerox_mfp.so.1.1.0 Looks like we picked up the last backend and made an extra symlink for it? I have installed fedora 10's rpm too, so perhaps that made the symlink as well? Oh, and the neat/screwy thing about this approach- I built from source without v4l support, but the existing 1.0.19 rpm had it, so now i get updated 1.1.0 backends, and the older v4l at the same time. allan -- "The truth is an offense, but not a sin"
