Hello,

I noticed several differences in the installation path of pcscd and libccid
on Ubuntu distros:

---- Under Ubuntu 08.04, pcscd is installed in:
/usr/sbin/
/usr/local/sbin

When I boot the computer, the running daemon is from /usr/local/sbin (I can
see that from ps aux | grep pcscd)

I also noticed that drivers are located in:
/usr/local/lib/pcsc/drivers
/usr/lib/pcsc/drivers

Some proprietary-driver installers (SCM for example) use pkg-config
libpcsclite --variable=usbdropdir to know where to drop the bundle driver
file. On Ubuntu 08.04 this variable equals /usr/local/pcsc/driver


---- Under Ubuntu 09.04, pcscd is installed in:
/usr/sbin/ (only in this directory)

drivers are located only in: /usr/lib/pcsc/drivers

pkg-config libpcsclite --variable=usbdropdir is empty thus the SCM prop
driver installs the bundle by default in /usr/lib/pcsc/drivers (value chosen
by the installer when the variable is empty). The driver is properly
recognized since pcsclite searches for the drivers in /usr/lib/pcsc/drivers.

---- Under Ubuntu 10.04, there is a whole mess:

pkg-config libpcsclite --variable=usbdropdir sends back
/usr/local/pcsc/driver, thus the SCM proprietary driver drops
everything in /usr/local/pcsc/drivers.
But upon start-up the daemon is launched from /usr/sbin/, thus pcsclite
searches for the drivers in /usr/lib/pcsc/drivers and the SCM driver cannot
be found (instead libccid is used but libccid has limited features with the
SCM device...).

Instead of trying to move files by hand and so on, I am trying to understand
what is happening and the rules. I searched in many docs but could not find
the solution.

Q1: Why are there sometimes two possible paths for install ? (local related
and *not* local related)
Q2: When is the usbdropdir variable initialized?


Thanks,
Franz
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to