[Bug] QMK doctor only checks /etc/udev/rules.d for udev rules.

[bbaserdem]

The doctor command in qmk python library fails to find the correct rules in /usr/lib/udev/rules.d directory.

Describe the Bug

The doctor command in QMK python library only checks a hard coded /etc/udev/rules.d for udev rules. Which works fine if you put your rules there. But these rules can also be located in /usr/lib/udev/rules.d; and actually is the preferred location for linux package managers to drop their udev rules. I recently packaged the python client in archlinux; and also provided neccessary udev rules along with it. After switching to these rules, I noticed I was getting warnings from qmk doctor when I had the correct udev rules in place.

System Information

• Keyboard: N/A
• Operating system: Archlinux
• AVR GCC version: 10.1.0
• ARM GCC version: 10.1.0
• QMK Firmware version: 0.9.46
• Any keyboard related software installed?
  • Karabiner
  • Other:
  • AutoHotKey

Additional Context

I also implemented a quick fix; and issued the pull request #9907

[zvecr]

As a note https://aur.archlinux.org/packages/qmk exists and mentioned in the install docs on Arch-based distros you can also try the qmk package from AUR (note: it’s maintained by a community member): yay -S qmk).

[bbaserdem]

@zverc The aforementioned package stealth installs python-hjson python package without seperately packaging it (very bad practice) and uses pip to do so (another bad practice). After I contacted the maintainer without response, (granted I did not wait longer than a day; but still has not responded) I repackaged both python-qmk and python-hjson in the AUR to fit archlinux packaging guidelines better; since I cannot change a package that another user has submitted. (unless the user adds me as a comaintainer)

In general; I'm against advertising any PKGBUILD in the AUR as an installation option. Pip installation instructions are sufficient in the docs.

[Foxboron]

Honestly, is hjson needed? It's used one place to somehow streamline the parsing of some JSON data. But it seems like a rather unorganized project with no releases since 2014. Could we check if it's possible to remove it?