New port in MacPorts and question about TokenD
Leonardo Brondani Schenkel <[email protected]>
| Newsgroups | gmane.comp.encryption.opensc.devel |
|---|---|
| Message-ID | <CAC7cz-sCxB7XzPGEn3h0t3DXMxmS5gTWHKW_iXZuWn5Ji6X6eQ@mail.gmail.com> |
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 [email protected] https://lists.sourceforge.net/lists/listinfo/opensc-devel