Arch Linux User Repository

A message to enable the server is output if it's not already enabled. Do you want a separate message for only temporarily enabling?

which they probably rarely have to do when most other services all are enabled and started by default

Please name some services for network software (which listens on all interfaces) packaged in Arch Linux that are automatically configured to start upon installation. I'm not aware of any.

(Someone else please correct me if I'm wrong.)

You can do both actions in one command using:

sudo systemctl enable --now teamviewerd

but I dnon't think it's obvious that if someone knows how to run 'yaourt -S', which they do hundreds of times, that they would know how to start a service

IMHO, Arch Linux is not the best Linux distribution for those users.

How about just some output after the install (from the command line at least) which shows the next steps for enabling the server (for those who want it). Although it appears that it's not hard to enable the service, but I dnon't think it's obvious that if someone knows how to run 'yaourt -S', which they do hundreds of times, that they would know how to start a service, which they probably rarely have to do when most other services all are enabled and started by default, without googling (which is easy, but just stating the commands would save time and be easier). For those who came here first expecting a bug than googling how to start (like me), the commands you need are:

sudo systemctl start teamviewerd

sudo systemctl enable teamviewerd

(Someone else please correct me if I'm wrong.)

All my tests show that the client doesn't run without the server running.

If that's true, that must be new - I've definitely used the client before without having to run any server.

I disabled autostart. All my tests show that the client doesn't run without the server running.

"not autostarting TeamViewer makes remote support impossible"

What does that mean? Presumably, if you can install a package from AUR, you can enable/start TeamViewer, right?

Auto-starting proprietary code, with a history of vulnerabilities, which runs unsandboxed... seems like a pretty bad idea.

As I understand, this package includes both the client and server, and many people (incl. myself) won't need the server component at all, nor do they want it running at any time.

This is a weird argument, if a person doesn't want to learn how to start systemd services or even how to copy-paste the command from post_install notice, maybe they shouldn't be using Arch Linux in the first place.

Supporting you is easy. I can be sure that you'll get the 40 character command right. I want a teamviewer package with which I could remote support your mom. Part of Arch best practice is knowing when not to follow it. I can make a separate package if you like.

I strongly disagree with the decision to auto-enable teamviewerd.service in .install, Arch best-practise is to not enable services with install, even if they are needed to run/are the installed program.

I've decided to disown this package because the teamviewer aur package has been upgraded to version 13. If anyone wants to maintain this package please do so.