Re: OSX installer of the CCID driver
Martin Paljak <[email protected]>
| Newsgroups | gmane.comp.lib.muscle |
|---|---|
| Message-ID | <CACsm3DXHapMSdb=AzR4toJc7J2wyFLK0T4fizHuXEDWhWm3+8Q@mail.gmail.com> |
Hola, On Tue, Jan 7, 2014 at 10:46 AM, Ludovic Rousseau <[email protected]> wrote: > 2014/1/6 Martin Paljak <[email protected]>: > As expected it is a nigthmare. Only because Apple do not upgrade the > driver they provide :-( Indeed, it would be nice to also be able to upgrade pcsc-lite itself, but well... One can vote with the wallet and buy something else (I'm trying to convince myself that this laptop I'm writing from is my last apple product I'm buying...) ... > > Some remarks: > - libusbx should soon be renamed libusb and available at http://libusb.info/ I tried with both libusb and libusbx and one just needs to replace the git url probably. I've lost track of usb libraries and neither fixed the problem for what I'm patching the driver in the first place, unfortunately. Maybe the .info version does, will try later. > - you use ccid at revision 6811. It may be better to use the revision > of the release you indicate: 1.4.14 The bundle version indicator in Distribution.xml should have no real impact, other than cosmetics (files shall be overwritten anyway). I wrote "latest version" in the readme thus no real released version intended :) But yes, when the installer becomes part of the release procedure it should be done for exact release revisions. > - indicate the CCID version that will be installed in > osx-ccid-installer/resources/welcome.rtf Good idea, in theory I'd like to be able to build against random revisions of either libusb(x|.info) (if needed) and revision of libccid. Those revisions (or versions) should also be visible in the installer automagically. > - indicate in welcome.rtf that you include patches I hope the patch shall be included in upstream, as it should be sufficiently localized so that the only people who would notice it would be people who notice the absence of the patch, because their device does not work :) > - what is the licence of your files and scripts? I may reuse some > parts of your package.sh Feel free to do so, my goal is to have one single and functioning driver installer for OSX. Once available, I'll delete the github repository. One thing to keep in mind would be ease of creating "branded" installers. That would be one incentive for upgrading for the users in the first place, and it would be better if the interested parties could release a functionally equivalent but differently branded driver installer, which could be upgraded with version x+1 without hassle, instead of generating an incompatible "ifd-ccid-vendor.bundle" or worse yet, ifd-ccid.bundle. Thanks, Martin