Comment 8 for bug 1892559

While looking at pcsc-tools and pcscs-perl (only needed for the dependency from pcscs-tools) I have found that these are not really depended on by anything important.

This matches the statement in the request that says:
"This package provides general utilities for smartcards; it's possible that we do not strictly need this package for our use case."

Use case wise it contains:
- /usr/bin/ATR_analysis
  Tool to analyze the raw ATR answer from a smart card - debugging tool at best and
  no common use case
- /usr/bin/scriptor + /usr/bin/gscriptor
  Send scripts to a smartcard, that might be a developer or debugging feature but doesn't sound
  an end user thing for the enterprise desktop you have in mind.
- /usr/bin/pcsc_scan
  This is the one end-user useful tool in this toolset showing the available cards that are
  inserted. But honestly you want to integrate things in an enterprise desktop and there I'd
  expect a UI-thing for it and not this cmdline tool. At the same time nothing in gnome or
  anywhere else related depends on it.

IMHO we should not promote packages to main we have no real use and integration of.

If there is a good case how this plays a role in the envisioned "Enterprise Desktop smartcard integration" then I'm more than happy to review and process this (in that case also say why/why-not pcscd is important - see above).

MIR Team Nack to pcsc-tools and pcscs-perl for the (currently) given dependencies and reasoning.