Arch Linux User Repository

@jahway603 To my knowledge, there is no need to do that. The recommended solution is for each package variant of the same software to provide the basic package (session-desktop here) then only conflict with that. This is described here.

Anyway, are you experiencing any issue now?

Please update Line 17 to include other conflicting packages https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=session-desktop-bin#n17

conflicts=('session-desktop' 'session-desktop-appimage' 'session-desktop-git')

works great, thanks for the quick fix!

@TomZander Thanks for pointing it out. My bad. I don't know why I added $pkgdir to the first path argument of ln. I should omit it to let the symlink point to the absolute location of the executable in the system after installation. I've updated the package. Please check if this solves your problem.

The suggested symlink solution is factually wrong.

The result is easy to observe, after installing the package you can do an ls -al /usr/bin/session-messenger-desktop

the result is a symlink that points to your AUR dir. Which is often in someone's homedir and thus failed to work for other users on my system. You should NOT put a symlink in the pkgdir like this. Using an install file would be much better.

ls -al /usr/bin/session-messenger-desktop
lrwxrwxrwx 1 root root 93 mei  3 10:20 /usr/bin/session-messenger-desktop -> /home/tom/data/pkg/session-desktop-bin/pkg/session-desktop-bin/opt/Session/session-desktop

Edit:

Forcing a relative symlink DOES work:

-    ln -s $pkgdir/opt/Session/session-desktop $pkgdir/usr/bin/session-messenger-desktop
+    cd $pkgdir/usr/bin
+    ln -s ../../opt/Session/session-desktop session-messenger-desktop

@escape0707 It was exactly from extra/chromium that I took it to be still a good thing to do security-wise. I'll dig through my notes and add more detailed info. Thanks for the speedy change!

@glitsj16 Thanks for the note. I've never saw related info on the Electron package guidelines page, but after some search, I decided to follow extra/chromium and give chrome-sandbox SUID. I would be grateful if you could leave some related documentation explaining the necessity of this, though.

The chrome-sandbox file needs to be SUID. That's a rather important security feature. Please correct this. A one-liner change: chmod 4755 $pkgdir/opt/Session/chrome-sandbox

Old unnecessary .install file removed from this package. If you see an error message saying /usr/bin/session-messenger-desktop already exists during your next update, you can simply sudo rm /usr/bin/session-messenger-desktop then redo the updating process.

It's because previously this package used a .install script to create the symlink in /usr/bin to the actual executable file installed in /opt, and thus this symlink is not managed by pacman directly. When you upgrade, pacman will frown upon this file and refuse to overwrite files it doesn't recoginzed yet. So just rm the symlink and restart updating again.

@post-factum Oh yes, you are right. I thought about changing these part when I applied to take over this orphaned package, but forgot it when the take-over happened. I'll look into it when I'm home.