Package: libpisock9 Version: 0.11.8-0.12.0-pre4-300rgc Followup-For: Bug #346319
The following is a proposal to actually enable the use of libusb, now that it is used for compiling the package. I believe it should be enabled only on explicit request from the user, since using it disables the use of the visor kernel module. Actually using libusb support requires two things: * Disabling tha autoloading of the visor kernel module, and * Setting correct permissions on the device entry on /proc/bus/usb The first is accomplished by a file in /etc/hotplug/blocklist.d containing the single word 'visor'. This however is probably no a sane default for the package, as it would break most everyone's configurations. The second issue can be handled by addapting the solution used by libsane. The files on http://nul-unu.com/quien/rodrigo/software/usbdevices.db and http://nul-unu.com/quien/rodrigo/software/pilot-link.hotplug should be added to the package, inside an /etc/pilot-link directory. With this in place, enabling libusb support is a matter of creating the file on /etc/hotplug/blocklist.d and creating a symlink from /etc/hotplug.d/usb to the /etc/pilot-link/pilot-link.hotplug file. This could be done by the postinstall script on response to explicit user request, I guess, or it could be left indicated in the documentation. -- Rodrigo Gallardo PGP Key ID: ADC9BC28 Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28 http://www.nul-unu.com http://www.nul-unu.com/blogs/elucubrando
signature.asc
Description: Digital signature
