Martin Pitt wrote: > Package: hal > Version: 0.5.11-3 > Tags: patch > User: [EMAIL PROTECTED] > Usertags: origin-ubuntu intrepid ubuntu-patch > > Hi! > > It already occurred several times to me that people had trouble with > FDI files which were apparently not "picked up" by hal. One particular > case is https://bugs.launchpad.net/bugs/275825, where I finally saw > the light: time-based comparison of .fdi files vs. the cache, as done > in di_cache_coherency_check(), doesn't work with dpkg, which maintains > the original file timestamps on unpack. > > The quick fix for this is to remove the cache in the init script, > which I just did in Ubuntu (we are close to release). It sacrifices > most of the startup speed improvement unfortunately, and hal still > won't pick up fdi changes immediately, but at least it will work after > a reboot. > > The more correct long-term solution could be to create a > dh_install_hal_fdi which generates > /usr/lib/hal/hald-generate-fdi-cache postinst snippets, and convert > all packages shipping .fdi files to use it. But that's not really > adequate for Lenny, and with DeviceKit being on the horizon, it might > be obsolete before we even finish.. >
Hi Martin, I had a short discussion with lool on irc, and we had an alternative idea: Install a dpkg trigger. For the etch -> lenny upgrade, we would regenerate the fdi cache in hal postinst as we can't rely on the dpkg triggers functionality yet. Do you see any downsides of this approach? It would we much less work than a dh_fdi and avoid the costly regeneration on each boot. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
