New review comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/34757#discussion_r815470055

Comment:
> so libmtp is broken on all the other distros then?

I don't know, I don't use other distros. Is there a different method to give users access to usb devices? The only methods that come to my mind are: (a) make the device group-readable by a well known group (b) run the programs that need to access the device as root (either setuid or sudo)  (c) have a daemon running as root that the programs talk to. I don't think libmtp has (c) and (b) seems unsafe so (a) is the only reasonable choice AFAICT.

> i would go with what gentoo does (`plugdev`), as that's used in some templates already

- `plugdev` is not documented here: https://docs.voidlinux.org/config/users-and-groups.html#default-groups
- I see three packages create group `plugdev`, namely `openocd`, `openrazer-meta` and `wally-udev-rules`, so maybe it's ok to use `plugdev` without underscore (the policy says to use underscore: "System accounts and groups must be prefixed with an underscore to prevent clashing with names of user accounts." except for old packages).
- debian says `plugdev`  "Allows members to mount (only with the options nodev and nosuid, for security reasons) and umount removable devices through pmount." (https://wiki.debian.org/SystemGroups)
- in void pmount is setuid root instead.

My rationale for `_libmtp` was that it is unambiguous what you are getting access to.