Mike Gerwitz <m...@gnu.org> writes: > Hey, Marius: > > I'm resurrecting this thread. :)
Hello Mike, long time no see! :-) > On Mon, Oct 31, 2016 at 10:09:14 +0000, Marius Bakke wrote: >> Mike Gerwitz <m...@gnu.org> writes: >>> 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. > > I'm getting GuixSD set up on an X200 now, and this is something that I'm > interested in getting resolved. For the time being, I'm using the > symlink workaround that you suggested. Cool, welcome to GuixSD land! > If you're still interested in doing this---great! Otherwise, I'm > tight on time and am already deep in a GuixSD crash-course, so I'd > appreciate any sort of mentoring/direction to get this working properly > and in a manner consistent with Guix/GuixSD's philosophy. If there are > existing service examples that demonstrate the same core concept, I'd be > happy to play around with that. Unfortunately I lost(!) my key token (luckily nothing important on it), but I'm happy to lend a hand (or take donations! :P). > But I'd need to know what approach you'd like to take to solving > this. Could you provide some more detail? I'd start by copying an existing (simple) service as "boilerplate", and then write a "system test" that simply (attempts to) start the daemon. You'll find these under "gnu/tests" and "gnu/services". Once you have that, you can run "make check-system TESTS=pcscd" (typically in a `guix environment guix`) to try out the service using a single command instead of reconfiguring a "real" system/VM. Then gradually add the bits needed to successfully start the service. Grepping around, "cups.scm" deals with some symlinks to "cups-filters" which may be useful, and there are also plenty examples of creating "/var/lib/foo" and other directories as required. The #guix channel on Freenode should be able to help out with most obstacles, in addition to this list for the tricky parts. Good luck! :-)
signature.asc
Description: PGP signature
