It is not about what I prefer. It's about what it (mis)represents. I get what you are trying to do, but this is not how it's done. You should try to work with @frealgagu and get chrome-remote-desktop
updated. If he does not respond in reasonable time, and the package is not maintained, you should create orphan request and then adopt the package if accepted.
And to the PKGBUILD itself, having SKIP for the sha256sum check of the .deb file itself is WRONG and should not be done!
Pinned Comments
frealgagu commented on 2020-12-05 22:38 (UTC)
I maintain the latest built package at:
https://github.com/frealgagu/archlinux.chrome-remote-desktop/releases/
victorbrca commented on 2020-04-03 01:04 (UTC)
Thanks @frealgagu for packaging this, @nightuser for the existing session patch and @Brinsky for the instructions.
I've compiled both instructions with screenshots and added it to my blog if anyone is having issues with the install. Otherwise, just follow the instructions in the comments by @Brinsky from 2019-12-06 13:58.
Brinsky commented on 2019-12-06 13:58 (UTC)
Here's how I got this working with the new web app (remotedesktop.google.com):
crd --setup
~/.chrome-remote-desktop-session
DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="<UNIQUE_CODE>" --redirect-url="<https://remotedesktop.google.com/_/oauthredirect>" --name=
crd --start