Closed ryanfitzsimon closed 1 year ago
What about just using ddcutil as binary path, then it is upto the user to have ddcutil in their PATH?
That would work fine for me personally (it's actually what I'm entering as the value for this setting).
I was concerned that it might break things for users that currently have /usr/bin/ddcutil
on their system, but don't have it on their path for whatever reason.
The extension would stop working when they upgrade, which could be frustrating even if the fix is straightforward.
Being able to easily specify the binary would also be nice for someone experimenting with different ddcutil
builds, but I imagine that's a pretty niche use case.
I will merge it, since you did the work already, it would be a waste.
This allows the extension to work on systems with ddcutil installed in locations other than /usr/bin/ddcutil.