I have a proposal for this package that I figured I'd run by you. To preface this, I'm not an expert in this area and this might be a very stupid question.
The NZXT controller conflicts with at least 1 other controller software (Gkraken) for pump and fan speed to control cooling. While the hardware continues to work, the ability to change cooling profiles is prevented. I assume this is because they both try to control it through the same USB interface. Gkraken doesn't have LED control and OpenRGB doesn't have fan/pump control and they are both the best at what they are intended to do in my opinion. Personally, I would much rather lose lighting control over cooling control.
A simple sed -i '/NZXT/s/.*//' OpenRGB.cpp
in the build process removes any calls to NZXT controllers and builds without NZXT support leaving other software to do that. Is it feasible and/or reasonable to create a warning about the possible loss of hardware control and a Y/n option if the user wants to build with or without NZXT control? Or do you think a separate package should be created, which ultimately would be identical to yours but with the one line added into the PKGBUILD?
Thanks
Pinned Comments