On Thursday 15 April 2010 23:48:42 Till Kamppeter wrote: > Problem is that hp-check depends on cups-config, which is in > libcups2-dev. Will we have to depend on libcups2-dev and pull in part of > the development stack with it? IMHO, hp-check is using a build time component (cups-config) to do its run time dependency checking. That is the issue. hp-check doesn't depend on cups-config, Without libcups2-dev it reports incorrectly (run time -r): $ hp-check -r [...] Checking for CUPS... Status: scheduler is running error: Version: (Not available. CUPS may not be installed or not running.) [...] Checking for dependency: CUPS - Common Unix Printing System... OK, found. As you can see from the results above, with libcups2-dev, hp-check does report correctly that the scheduler is running, and that the runtime dependency for CUPS is met. The thing it cannot determine without cups-config is what version of CUPS we are running. > WDYT what should we do? Replace the runtime call on cups-config with something that will give the version of the installed CUPS. Unfortunately none of the binaries shipped with cups appear to report their version: cups: /usr/sbin/cupsd /usr/sbin/cupsfilter cups-client: /usr/sbin/lpadmin /usr/sbin/cupsaddsmb /usr/sbin/lpinfo /usr/sbin/lpmove /usr/sbin/cupsctl /usr/sbin/cupsaccept /usr/bin/cancel /usr/bin/lpstat /usr/bin/lppasswd /usr/bin/cupstestdsc /usr/bin/lpoptions /usr/bin/cupstestppd /usr/bin/lp /usr/sbin/reject /usr/sbin/accept /usr/sbin/cupsreject /usr/sbin/cupsenable /usr/sbin/cupsdisable I would suggest with discuss with CUPS and get an Version string printed out, possible against; lpinfo and/or cupsd -t. In the meantime I would move hp-check back into hplip and accept that we will get some false reporting, as shown above. Mark
Attachment:
signature.asc
Description: This is a digitally signed message part.