Package Details: omnikey_ifdokccid 4.3.3-4

Git Clone URL: (read-only, click to copy)
Package Base: omnikey_ifdokccid
Description: PCSC driver for OMNIKEY 1021, 3x21, 6121,512x, 532x
Upstream URL:
Keywords: omnikey pcsc
Licenses: custom:HID_OK_Drivers_EULA
Conflicts: omnikey_ifdokccid-git
Submitter: onestone
Maintainer: JulianXhokaxhiu
Last Packager: JulianXhokaxhiu
Votes: 18
Popularity: 0.000000
First Submitted: 2015-03-04 04:02 (UTC)
Last Updated: 2019-04-21 15:42 (UTC)

Latest Comments

1 2 3 Next › Last »

abouvier commented on 2018-05-22 00:32 (UTC)

Yes, but I hope I'm not the only one :p

JulianXhokaxhiu commented on 2018-05-21 16:45 (UTC)

I hope you're happy now :)

abouvier commented on 2018-05-21 16:06 (UTC)

I think you misunderstood the purpose of the arch directive :p

Even if the package can be compiled for every arch, you should list all these arch in the array. any is for architecture independent package.

As this package is already compiled, and the ARM version is a 32-bit executable, the array should not accept aarch64 or any incompatible ARM arch.

JulianXhokaxhiu commented on 2018-05-21 15:36 (UTC)

At the current status the arch=('any') is because Arch supports i686, x86_64 and ARM ( through its various types ), so typing any would successfully met all of them ( the arm library contained in the omnikey zip works since ARMv5 and more ).

Related to prepare() and unzip I'll take care of them on the next version bump. Thanks for the hint :)

abouvier commented on 2018-05-21 13:07 (UTC) (edited on 2018-05-21 13:08 (UTC) by abouvier)

You should not use arch=('any') when the resulting package contains architecture dependent files (like

The extraction phase should rather take place in the prepare() function.

And the unzip makedepends seems unused :p

JulianXhokaxhiu commented on 2018-05-21 08:53 (UTC) (edited on 2018-05-21 08:53 (UTC) by JulianXhokaxhiu)

Package is now multi-platform enabled. It supports i686, x86_64 and arm too. Enjoy!

Alad commented on 2017-09-25 18:25 (UTC) (edited on 2017-09-25 18:26 (UTC) by Alad)

Submission date isn't the only consideration. Here, omnikey_ifdokccid you want to merge into this package is named directly after the source. omnikey_cardman_5x2x is named after one model, when multiple are mentioned in the description. Personally I'd be inclined to merge things the other way around for clarity. But I think you should talk to the maintainer of the other package first; maybe you both can co-maintain it.

abouvier commented on 2017-09-25 13:36 (UTC) (edited on 2017-09-25 14:23 (UTC) by abouvier)

You should asks for a merge then ;) By the way I think a better name would be pcsc-omnikey (like pcsc-cyberjack). Or ccid-omnikey, I'm not sure :p

mlq commented on 2017-09-25 13:28 (UTC)

It's basically the same as this one, but this one exists since 2010 and the other one since 2015.