@sixtyfive : you get this error because you haven't installed the drivers (e.g: ccid or acsccid depending on your reader).

Thank you! It's starting up fine now. Would it be possible to make both of these dependencies to 'pcsc-lite'? (I've installed both as I wasn't sure which one I needed and they don't seem to conflict).

For the dependencies, I don't know because it would mean that some useless drivers would be installed (e.g: people who need ccid may not want to have acsccid and vice-versa). I'll let the Solus experts advise on this and follow their recommendation.

I mean, we have nvidia drivers installed by default. How big are the package sizes of ccid and acsccid?

Installed, 150KB and 146KB respectively.

I mean, we have nvidia drivers installed by default

No we don't - we have xorg nouveau driver installed.

Which noone having an integrated GPU only uses, his point prolly?

Derp, yes ikey is right *smack head*. Anyway @kyrios123 I don't see a problem with adding both acsccid and ccid as rundeps as they are super small and don't rely on anything.

Or we could do the other way around: define pcsc-lite as a dependency of ccid and acsccid (this would make more sense since pcsc-lite-devel is a build dependency of these packages)

As a user, it goes like this:

"My online banking is Jameica"

"Jameica says it needs PCSC to connect to my card reader"

"eopkg sr pcsc"

"Oh cool, there's 'pcsc-lite'"

"eopkg it pcsc-lite"

So, not sure about going the other way around...

In T5095#91602, @kyrios123 wrote:

Or we could do the other way around: define pcsc-lite as a dependency of ccid and acsccid (this would make more sense since pcsc-lite-devel is a build dependency of these packages)

Just noticed I claimed this task then nothing was done since people have different view on what should be done. I still believe that the proposal I made is the right way to set the dependencies. And since it is foreseen to have one day hotplug driver installation, when the user will plug a card reader, the ldm will install the appropriate driver and the driver will request pcsc-lite and the system will be ready.

If we proceed the other way around, in addition to the ugly cross dependencies, the user will plug the card reader, ldm will install the correct driver then the user will have to manually install pcsc-lite (which is dumb imo), and pcsc-lite will also install an unnecessary driver.

Guys & girls, any thoughts about this ? What shall we do ?

First thought that comes to mind: atm there's no ldm yet. So make the driver a dependency of the software now and then swap it when hotplug driver installation has arrived, on which, if I understand you correctly, there's no eta anyways.

I just got this error. Let me say it's very counterintuitive to install and run pcsc-lite and see it does nothing because the driver are missing. I think every user expects to install it, start its systemd service and profit.
Before working at home, I was using pcsc-lite on Fedora at work and in fact ccid is among the recommended deps. Now I know eopkg doesn't have such a feature, still I think we should facilitate the average user.

@kyrios123

Guys & girls, any thoughts about this ? What shall we do ?

In my opinion it's better to add ccid and acsccid as deps of pcsc-lite. A user shouldn't be required to know what driver they need, they should only install the library because that's what they need to interact with their card reader. Plus, people nowadays are forced to install tons of Electron apps (yuk!), I think that it's perfectly viable to install less than 1 MiB of drivers.

FWIW Debian installs libccid along with pcscd.