On Sat, 10 Aug 2013, Phil Dibowitz wrote: > I think that it simplifies the code a *lot*, it's one implementation across > all platforms (we should be able to drop the windows code too), it's what the > libusb developers recommend (which means that it'll get into more and more > distros), and it's a bunch of code we don't have to maintain. > > I'm happy to do nagging of the distro people, I just stopped paying attention > at some point... but hidapi is the easiest thing int he world to package. It's > one file, and the git version supports building a shared library right out of > the box. > > We could do a grace period though where we have both for two versions and a > bunch of warnings if you compile with the libusb version. > > It also moves us to libusb-1.0 (we're on 0.1 at the moment) which... if we're > going to re-write that layer, we might as well move to the right thing.
On the other hand, it's not like the libusb code has required a lot of maintenance. I made one small fix in January, and before that, the code hadn't been changed since 2010. On the packaging issue, it's not the technical aspect that I'm worried about -- it's the administrative part (getting sponsors, getting packaging reviewed, etc). The fact that we'd require a git version makes it even more complicated. Someone already tried to get hidapi packaged in Fedora and gave up. Yeah, I think at the very least, we should do some sort of transition period. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
