Set udev rules for YARP devices that require administrative rights

[PeterBowman]

Currently, there are two desktop shortcuts in scripts/gnome/ due to the need of launching the serialport device with sudo (ref). This is handled via gksudo, see:

amor-configuration-files/scripts/gnome/amor-apps-sudo.desktop

Line 5 in 45b16d5

Exec=gksudo -k -u root yarpmanager

A better option: keep one single shortcut file and install udev rules for offending devices.

Examples of udev rules:

• https://github.com/roboticslab-uc3m/amor-api/blob/803c187/scripts/10-amor.rules (private)
• Se debe configurar y documentar configuración PC nuevo de Blacky asrob-uc3m/impresoras-asrob#2
• Se debe configurar y documentar PC nuevo de Hija Resurrection asrob-uc3m/impresoras-asrob#3

[jgvictores]

Related: asrob-uc3m/yarp-devices#14

[PeterBowman]

Another example (private repo, so copy-pasting):

/scripts/CMakeLists.txt@roboticslab-uc3m/amor-api

if(UNIX)
    configure_file(${CMAKE_SOURCE_DIR}/cmake/templates/10-amor.rules.in
                   ${CMAKE_BINARY_DIR}/10-amor.rules)

    install(PROGRAMS amor_init_can.sh
            DESTINATION ${CMAKE_INSTALL_BINDIR}
            COMPONENT udev
            RENAME amor_init_can)

    install(FILES ${CMAKE_BINARY_DIR}/10-amor.rules
            DESTINATION /etc/udev/rules.d
            COMPONENT udev)
endif()

/cmake/templates/10-amor.rules.in@roboticslab-uc3m/amor-api (hiding ids out of paranoia)

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="xxxx", ATTR{idProduct}=="xxxx", RUN+="${CMAKE_INSTALL_FULL_BINDIR}/amor_init_can"

...and Cpack support: https://github.com/roboticslab-uc3m/amor-api/commit/5c76580014ff1c0f324c1e64bd202c5689667956.

[PeterBowman]

Might be useful: https://github.com/greatscottgadgets/ubertooth/blob/a6332a7d0b74c9becf5d250111c5b222333faa0a/host/misc/udev/CMakeLists.txt.