> Yeah, that was bad. You did also see my screencast, right? :-) > Yes I first saw the screencast actually >> If something could be done in libbeidlibopensc2, it's to make a silent >> test about /var/run/openct/status (or cf ct_format_path() ) before >> calling the openct lib (/src/newpkcs11/src/libopensc/reader-openct.c) >> but it's quite ugly. >> > > I don't think so. Verifying whether something is there before using it > seems like proper coding to me. > I though the duplication of code is ugly but then I saw that the path retrieval is in ct_format_path() and available, so it's ok cf /usr/include/openct/path.h from libopenct1-dev >> So one immediate way would be to document the option reader_drivers >> > I could do that, but many people will miss it. > Without documenting it, for sure they'll miss it ;-) > [...] No, that would be debconf-abuse. I see no need to use debconf here You're the boss ;-) Silent detection within libbeidlibopensc2 is the best way. Maybe sth to forward also to the libopensc2 guys?
Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
