hidapi 0.9.0

[z3ntu]

hidapi has a new home at libusb - and 0.9.0 has been released

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

[fxcoudert]

It looks more like a fork than a new home. The old page still exists, there is no redirection, and the new page has very little following. Is there an official announcement about the situation?

[z3ntu]

Yes, it's a fork because @signal11 hasn't been active at all for a while now and hidapi hasn't seen any activity in the original repository since January 2016 resulting in a number of different forks with open (partly very important) patches applied.

Quote from the libusb/hidapi readme:

It was moved to libusb/hidapi on June 4th, 2019, in order to merge important bugfixes and continue development of the library.

See also signal11/hidapi#373

[Youw]

The old page still exists, there is no redirection

that can be changed only by the original author, and since he's not answering for so long, the only thing we can do is to assume, that he "got hit by a bus"

still, the project needs to be maintained and libusb maintainer(s) kindly agreed to host hidapi's fork for its further development

signal11/hidapi#373 is the most official discussion, we can have now

also, every time, when there is a new open bug/PR/etc. in https://github.com/signal11/hidapi repo, we (new maintainers) giving a comments with links to https://github.com/libusb/hidapi and briefly explain, why a new repository exists; that strategy works so far - new PRs are coming along

[melMass]

I'm using brew's hidapi but just realized it uses the old signal11 one. What is the status of this pull request?

[SMillerDev]

I just checked and even the authors webdomain stopped responding to requests. I think it might be good to let libusb take over here, though I would like to see a link referencing either this issue or the upstream one in the formula.

[z3ntu]

I've changed the commit message to include the two issues.

[Qbicz]

@fxcoudert @SMillerDev can we merge this?

[fxcoudert]

@BrewTestBot test this please