Arch Linux User Repository

Thanks kuhtoxo for taking the maintenance of the package! :)
I just want to make a few remarks, as the recent update made this package divert from arch packaging guidelines and best practices:

• Files get copied in place using the .INSTALL script instead of doing that during the packaging (PKGBUILD's package() function). This prevents pacman from properly tracking files installed by the package, thus breaking things like file conflicts handling, or querying which package owns a file (eg., pacman -Qo /usr/share/applications/rustdesk.desktop returns that no packages own this file). You should always install files in the definitive location during package() unless you have a solid reason not to.

• According to the wiki (and more generally to man 7 file-hierarchy), units provided by packages should be installed in /usr/lib/systemd/system/. This allows the administrator to override (or mask) the unit file using /etc/systemd/system/ if needed.

• You should not stop a service pre-upgrade, especially for a remote control tool (what if I run the upgrade while I'm connected remotely to the computer?). Doing that is the responsibility of the administrator, automating it goes against the principle of simplicity of Arch. More generally speaking, you shouldn't interact with systemctl in packages; starting/stopping/enabling/disabling services is outside the scope of the package maintainer.
  ​
  If you deem it's absolutely necessary to restart the service (eg. because the application breaks when its files are updated while running), you can use a pacman hook that will restart the service using /usr/share/libalpm/scripts/systemd-hook reload rustdesk.service (that script makes sure we aren't in a chroot before invoking systemctl; it will do a restart when the unit doesn't support reload).
  ​

• Not an issue itself (it's more like to keep things clean), but you only need to conflict against rustdesk. Other packages you added to the list already provides rustdesk, so they will correctly conflict with your package without explicitly listing them :)

Look like it might be resolved with 1.3.0, I get just a warning now rustdesk[114703]: Cannot load libcuda.so.1. But the service does start.

@denton, I tested rustdesk system daemon in Manjaro KDE 6.6.47-1-MANJARO (64-bit) on AMD system. Everything works fine without additional packages.

In the package from the developers https://github.com/rustdesk/rustdesk/releases/download/1.3.0/rustdesk-1.3.0-0-x86_64.pkg.tar.zst there is no libcuda dependency.

Perhaps you should contact the rustdesk developers with your problem.

System daemon cannot be started without libcuda installed, even on an AMD system :(

@kuhtoxo installing directly from the github package everything works thanks for the reply.

and ya installing the 2 packages helped with yours thanks very much for your help.

@anasgets111, this package has two optional dependencies:

libappindicator-gtk3 (optional) – tray icon
libayatana-appindicator (optional) – tray icon

Try installing them.

Try deleting the package and installing it again if the package was installed earlier.

This package is based on the official package and repeats all dependencies from the official package https://github.com/rustdesk/rustdesk/releases/download/1.3.0/rustdesk-1.3.0-0-x86_64.pkg.tar.zst

Try to uninstall rustdesk-bin and install the official package directly. If this does not help, then you need to contact the rustdesk developers.

package from cachyos repos shows a system tray (gnome with tray extension) but isn't working,

this one is working but can't get it to show the tray.

@kuhtoxo. Thanks for your work.

@d-air 1, @ivanmara, @bone thanks for your comments.

Initially, I only planned to copy everything that is in the developer package from github.

I think your comments are reasonable, so I made the necessary changes and sent a new commit with version rel=2 (because this is a fix for the package build).

I only left the installation and removal of the service when deleting the package.

Hi

Thank you for maintaining this package!

Can you please remove any enable/disable and service restart steps from the install/upgrade script? Arch Linux packages do NOT do any auto restarts of anything let alone "auto-enable" during package install or upgrade.

Please stick to the "Simplicity" principle of Arch Linux: https://wiki.archlinux.org/title/Arch_Linux#Simplicity Quote: "It does not add automation features such as enabling a service simply because the package was installed"

Looking forward to a patch in this regard! Thank you!