No, it doesn't.
${_install_dir}
is a relative path and I only ever call it when touching things inside of ${pkgdir}
for packaging; now, ${pkgdir}
IS an absolute path, but I don't define that, makepkg
does.
That being said, the only way that can go wrong is if your system somehow misinterprets what ${pkgdir}
means. That's completely out of my hands.
Additionally, you might have your drive mounted via your desktop environment instead of /etc/fstab
; in which case, I advise you mount with fstab instead to minimize other potential interferences on your system. That said, I'm not responsible for the reason why.
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.