From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36765) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1flvtk-0003Wz-3g for guix-patches@gnu.org; Sat, 04 Aug 2018 08:43:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1flvtf-0007yd-3C for guix-patches@gnu.org; Sat, 04 Aug 2018 08:43:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:35444) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1flvte-0007yO-Uz for guix-patches@gnu.org; Sat, 04 Aug 2018 08:43:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1flvte-0007rD-IH for guix-patches@gnu.org; Sat, 04 Aug 2018 08:43:02 -0400 Subject: [bug#32358] Add pcscd service Resent-Message-ID: From: Arun Isaac In-Reply-To: <87a7q2lqc6.fsf@garuda.local.i-did-not-set--mail-host-address--so-tickle-me> References: <87a7q2lqc6.fsf@garuda.local.i-did-not-set--mail-host-address--so-tickle-me> Date: Sat, 04 Aug 2018 18:12:19 +0530 Message-ID: MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Chris Marusich Cc: 32358@debbugs.gnu.org > What problem does this pcsc-lite-bootstrap package solve? It looks like > you added pcsc-lite-bootstrap in order to avoid a cyclic dependency > between ccid and pcsc-lite. That seems fair, but is there any other > reason that I'm missing? No, there is no other reason. I only created pcsc-lite-bootstrap to avoid a circular dependence between ccid and pcsc-lite. > Do you know what the intent behind the --enable-usbdropdir option is in > (1) the pcsc-lite configure script and (2) the ccid configure script? I > checked the README in the source for both of these packages, but I > couldn't quite understand the intended use. It wasn't clear to me if > the usbdropdir directory is where the ccid/pcsc-lite expect to _find_ > drivers that the user makes available, or if this directory is where the > packages will _install_ their own drivers (or both, perhaps). I thought about this too. As far as I understood, the usbdropdir of the ccid package is where it installs its drivers, and the usbdropdir of the pcsc-lite package is where it expects to find drivers. > If the usbdropdir is intended to house additional drivers that the user > can "drop" in and use at runtime, then users of pcsc-lite/ccid might > reasonably expect to be able to easily add additional drivers to the > default configuration. If that's the case, then we might want to think > about how we can give a user the ability to configure additional > drivers. For example, if we gave the pcsc service configuration a field > like "usbdropdir-drivers" (e.g. a list of packages or file-like > objects), we could arrange for the union of those drivers to be placed > into the usbdropdir for pcsc/ccid to use. Good idea. I'll add a usb-drivers configuration field and send an updated patchset.