@Neko-san While your pinned method of setting permissions will technically work, it will break pacman permissions. (In my opinion,) a more preferred method would be to set an access control list to let members of the newly created group write into the unreal-engine folder. Just like how you setup Android Studio on Arch Linux. (https://wiki.archlinux.org/title/Android#Making_/opt/android-sdk_group-writeable)
# groupadd unreal-engine
# gpasswd -a <user> unreal-engine
# setfacl -R -m g:unreal-engine:rwx /opt/unreal-engine
# setfacl -d -m g:unreal-engine:rwX /opt/unreal-engine
This will maintain root:root disk permissions, thus matching the permissions in the package file and making pacman happy, while also giving the group unreal-engine rwx access to /opt/unreal-engine. But hey, you know, that's just like uh, my opinion, man.
Pinned Comments
Neko-san commented on 2022-11-01 02:32 (UTC) (edited on 2023-06-25 01:19 (UTC) by Neko-san)
@juancarlospaco this is easily done on your own system, not in a PKGBUILD, given that building packages runs as root:
Permission issues like this are already mentioned on the UE Arch wiki page: https://wiki.archlinux.org/title/Unreal_Engine_4#Installing_from_the_AUR
This is a user system problem; I already did what I could without needing users to do the above by giving the
777
permissions. If it still gives you trouble, you'll have to use the example to solve it or change the install location to somewhere you have user permissions by default (as I cannot do this for you).zerophase commented on 2021-05-27 08:15 (UTC) (edited on 2021-05-30 08:41 (UTC) by zerophase)
Will update to 5.0 when it is released.