Advertisement
ZirconiumX

Untitled

Feb 7th, 2019
142
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.02 KB | None | 0 0
  1. Thank you for your efforts, but you should have asked us before doing this.
  2.  
  3. Corsair have a tendency for unannounced breaking changes in their protocols, with no help provided to us for deciphering the resulting new protocols. Examples of this would be:
  4. - the recent rollout of firmware version 3 changing the USB endpoint configuration.
  5. - the K95 Platinum and MK.2 series introduced a new hardware profile format which we still have not deciphered, and so don't support due to legal issues of distributing an opaque binary blob.
  6. - the Dark Core and K63 Wireless use a different firmware format requiring special update procedures.
  7. - the Harpoon Wireless uses an entirely new protocol.
  8.  
  9. Corsair provide no way to downgrade firmware on Windows, which means a CUE firmware update could break compatibility with an older version of CKB.
  10.  
  11. In light of this, development of ckb-next usually moves much quicker than these distributions (especially Ubuntu), and we don't want to be receiving bug reports about older versions of our code, especially because manpower is stretched very thin already (there are two maintainers for this software, and going by stars alone that's a 400:1 user:developer ratio).
  12.  
  13. ckb-next relies on its community to provide [a PPA repository](https://launchpad.net/~davidmeikle/+archive/ubuntu/ckb-next-daily) of recent builds, and the extra manpower would be in my opinion better redirected towards updating that repository than merging our code into the Debuntu repositories. Alternatively, you could provide a third-party Debian-specific repository.
  14.  
  15. As more specific feedback to your commits:
  16. - We would prefer the manual pages to be automatically generated if possible; it's going to be a maintenance burden to manually update them every time we add a command line option otherwise
  17. - Typo fixes and removing the desktop encoding settings look good, thank you for catching these.
  18. - As mentioned, we'd rather not have this in the Debian repositories, but we'll probably include your CMake flag to help third parties package this.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement