all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Mike Gerwitz <mtg@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: Add ccid.
Date: Mon, 31 Oct 2016 10:09:14 +0000	[thread overview]
Message-ID: <87funcsud1.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <878tt5dyao.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

Mike Gerwitz <mtg@gnu.org> writes:

> Marius:
>
> Sorry for the late reply.
>
> On Fri, Oct 28, 2016 at 12:27:29 +0100, Marius Bakke wrote:
>> Packages are not allowed to write to /var, so to run pcscd on Guix you
>> will have to symlink ~/.guix-profile/pcsc/drivers to
>> /var/lib/pcsc/drivers manually, until we have a system service for
>> pcscd. Can you try that?
>
> That does indeed work.  Thanks.

Thanks a lot for testing! :)

> Part of this for me is being unfamiliar with how everything in Guix
> works, so I'm sure it'll make a lot more sense once I see what service
> you come up with and observe its conventions.

I haven't started working on this yet, but the idea is to provide a list
of drivers in the service definition (with ccid as default), and then
symlink each of them to the driver directory before starting pcscd.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

  reply	other threads:[~2016-10-31 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  9:46 [PATCH 1/1] gnu: Add ccid Marius Bakke
2016-10-28  4:18 ` Mike Gerwitz
2016-10-28 11:27   ` Marius Bakke
2016-10-31  2:53     ` Mike Gerwitz
2016-10-31 10:09       ` Marius Bakke [this message]
2017-11-20  4:11         ` Mike Gerwitz
2017-11-21  1:05           ` Marius Bakke
2017-11-21  2:11             ` Mike Gerwitz
2016-10-28 12:46 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87funcsud1.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mtg@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.