Anyway, I don't think kodi should be dependent on any unnecessary privileged commands to run. Having it to rely on a carte blanche sudoers file for the user account calling kodi seems a bit unsafe. (and the default sudoers file for the pi user account on raspbian got me really surprised - pi is by default by all standards really a root account, really strange security model)
I agree with the first part, but that will always be needed, if you want Kodi to work fine, with all features.
You always need to change udev rules, add the user to many groups to do something, etc. It doesn't matter which Kodi version you use. This is also true for other Linux OSs and platforms. Either you or the package maintainer.
Also, If you take a look at /usr/bin/kodi-standalone of the Kodi 15.2 from the Raspberry Pi Foundation repo, it also uses sudo, to "fix the black screen on exit" bug. This Kodi version (PiPplware's) uses the same debian package scripts from the one on RPi Foundation repo, which are this http://michael.gorven.za.net/bzr/debian ... d:/debian/
that are based on Ubuntu ones, only slightly changed for the Raspberry Pi. I changed /usr/bin/kodi, to fix also that bug and other ones and they also need sudo.
Other options would be editing the sudoers file, changing the permissions of the respective binaries to be possible to run them as "normal user", or run it as root. All that options seem worse in my opinion.
The user "pi" is not a root account, it is different. If I remember correctly, the major diference to, for example, Ubuntu, is that user "pi", compared to a default user, it has the "ask for password" for running something with sudo disabled. There are things you cannot do with the user pi, as is. But if you know how, you can always do everything, of course
And yeah, it is a bad decision in my opinion.
So if you want to run Kodi as another user, with all features and working fine, I recommend adding it to the sudo group and disable the password asking for the programs that are needed, until a better way is found.