Re: [Opensc-devel] New port in MacPorts and question about TokenD

[Martin P. <ma...@ma...>]

Hello,

It better be +tokend in this wording. Think of OpenSC.tokend like
out-of-tree PKCS#11 or Minidriver interface of OpenSC. It could also be
bundled inside OpenSC code tree as well (but is not, for historical
reasons).

For some reason (IMHO) it feels like MacPorts is more about things that
don't integrate with OSX that deeply (unlike the standard .pkg/.dmg
interface) and thus only to provide PKCS#11 and command line tools by
default.

But it could also be a separate package.

The reason for calling libopensc a "deprecated library" is only to
encourage developers to build against "proper interfaces" like PKCS#11 or
some platform-specific interface, not to make it impossible to build a
component-based OpenSC.

Best,

Martin

On Tue, 27 Sep 2016 at 21:57 Leonardo Brondani Schenkel <
leo...@gm...> wrote:

> Hello all,
>
> I have recently submitted a port for OpenSC in MacPorts:
> https://trac.macports.org/ticket/52372
>
> The port has been accepted and I volunteered to be the maintainer. I'm
> a long time user of both OpenSC and MacPorts, so I hope that this port
> will be useful for other Mac smartcard users — maybe some of them
> members of this very list.
>
> The port as it is now does not build the TokenD, though. This is what
> I want to introduce next and that's the reason why I'm posting. Since
> TokenD needs the OpenSC sources when building, I would like to know
> how exact must be the match between the OpenSC sources that were used
> by TokenD and the sources used to build the version of libopensc that
> is available at runtime. This will determine if TokenD can be a
> separate opensc-tokend port which is installable on its own (but
> dependent on opensc) or it will be a new "+tokend" variant of the
> opensc port (variants in MacPorts are like USE flags in Gentoo that
> can be used to turn on/off features when building packages).
>
> I strongly suspect that they must be built together or you risk
> running into a world of pain when a libopensc gets upgraded and you
> have a TokenD built against and older version (or vice-versa), but it
> does not harm to ask the list.
>
> I already have a successful build of TokenD built via MacPorts on my
> machine, so the outcome of this discussion will determine how I'm
> going to submit this work to MacPorts. Any suggestions on the matter
> are greatly appreciated.
>
> Thank you,
> Leonardo.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Opensc-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>