[Pcsclite-muscle] New version of pcsc-lite: 2.3.1
Ludovic Rousseau
ludovic.rousseau at gmail.com
Fri Dec 27 09:02:44 PST 2024
Le ven. 27 déc. 2024 à 15:41, Greg Troxel <gdt at lexort.com> a écrit :
>
> Ludovic Rousseau <ludovic.rousseau at gmail.com> writes:
>
> >> The big question for me is: did anything change about config file
> >> placement/reading other than installing this file? If not, I can just
> >> not install it and do the update, and if so, I don't feel that I can
> >> commit the update without untangling the config file location/reading.
> >
> > This file is supposed to be used/read by the launching system (systemd
> > for example).
> > It is NOT used by pcscd. But it defines environment variables used by pcscd.
> > It is supposed to be edited by the local admin.
> >
> > If you do not have an equivalent on NetBSD you can ignore it.
>
> We don't have any concept of launchers setting environment variables,
> and generally daemons don't look for config in the env. They read
> e.g. $prefix/etc/pcscd/pcscd.conf. (FWIW, my take on best practices is
> that the defaults make sense so that many people do not need a config
> file, so that it is normal for that file to be missing if one intends to
> be default.)
>
> Should this be conditional on HAVE_SYSTEMD? It seems like a systemd
> special case rather than broader practice.
It is not specific to systemd.
The same mechanism was already used by SysVinit previously used on Debian.
For example see
https://salsa.debian.org/debian/pcsc-lite/-/blob/master/debian/pcscd.init?ref_type=heads#L33
> For pkgsrc, I have just patched the install out of the meson file.
OK
Bye
--
Dr. Ludovic Rousseau
More information about the pcsclite-muscle
mailing list