In its current form we cannot accept this PR. This invalidates other distro's that don't set up a plugdev group -- anything systemd-based should be running with TAG+="uaccess" instead, as per the systemd developers (https://bugzilla.redhat.com/show_bug.cgi?id=815093#c2).

For example, with my main Fedora machine I don't have a plugdev group -- if we merge this PR should I subsequently raise a bugfix PR reverting to TAG+="uaccess" as that fixes my system?

The vast majority of distros use systemd nowadays, and whilst you may not find that selection palatable, you're the outlier.

From your perspective I'd suggest manually modifying the rules and installing that as per your system requirements, or figuring out an automated way to select one of two different rules files -- with preference being the TAG+="uaccess" route wherever available.

Remind me to read the actual changed lines next time -- I see the TAG+=uaccess wasn't removed. Let me confirm that this still functions correctly.

having both MODE/GROUP and TAG makes it work with and without systemd/elogind. it's a common pattern across packages on distros without mandatory systemd/elogind

@tzarc By the way, in terms of confirming, on one of these lines the MODE and GROUP has been present for a long time already. Without issue as far as I can tell. Good to manually verify of course, but just so you know. Plus, as @classabbyamp mentions, it's a common approach.