Package Details: unreal-engine 5.5.0-0

Git Clone URL: https://aur.archlinux.org/unreal-engine.git (read-only, click to copy)
Package Base: unreal-engine
Description: A 3D game engine by Epic Games which can be used non-commercially for free.
Upstream URL: https://www.unrealengine.com/
Keywords: 3D engine game ue5 Unreal
Licenses: GPL3, custom:UnrealEngine
Submitter: acerix
Maintainer: Shatur (Neko-san)
Last Packager: Neko-san
Votes: 76
Popularity: 1.03
First Submitted: 2016-05-01 18:37 (UTC)
Last Updated: 2024-11-16 03:10 (UTC)

Dependencies (29)

Required by (1)

Sources (6)

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:

sudo groupadd unrealengine-users
sudo usermod -aG unrealengine-users (your-username)
sudo chown -R root:unrealengine-users /opt/unreal-engine
sudo chmod -R 775 /opt/unreal-engine

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.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 81 Next › Last »

seqfault commented on 2023-06-23 18:50 (UTC)

@OdinVex: thanks a lot for your time, I think I get it now.

OdinVex commented on 2023-06-23 18:48 (UTC) (edited on 2023-06-23 18:50 (UTC) by OdinVex)

@k1gen For the second/third? time, you cannot makepkg -i until you complete the PACKAGE process from building...That is a part of -s, which normally 'builds' and then 'PACKAGES', but if you modify what I told you to then you can skip the actual effective-building (while keeping the src left alone) and make it PACKAGE it so that you can makepkg -i it. Just do what I said about build(), prepare(), and add the icon script changes to correct that. Then makepkg -s (which 'builds and packages' but in this case will skip effective building and simply package), then makepkg -i. You probably need more experience with Ubuntu or Mint (loved Cinnamon but it was based on old packages, agh). And you won't be copying the PKGBUILD from here. makepkg will error about everything not matching up to the original repo. Stop trying to shortcut your situation avoiding editing the PKGBUILD, or you'll just end up forcing yourself abandon and redo the entire thing.

seqfault commented on 2023-06-23 18:43 (UTC)

@OdinVex: so I just copy latest PKGBUILD from here and edit it like this, then makepkg -i, and makepkg will keep my src dir?

OdinVex commented on 2023-06-23 18:34 (UTC) (edited on 2023-06-23 18:38 (UTC) by OdinVex)

@Neko-san I'm a fan of administrators being administrators, and I despise sudo. But you're entitled to your headache-relief. :)

@k1gen A git pull won't work correctly at all, you'll just get error after error. You must edit the PKGBUILD in this situation, it'd be so much easier to fix all this if you did. PKGBUILD is the same as SH.

Neko-san commented on 2023-06-23 18:32 (UTC)

@OdinVex I understand what you mean, and if someone really wants to do that at the cost of issues, they can still find the binary or modify the script themself. I'm not going to troubleshoot short-sighted insecure 'root everything' nonsense. That aside, /opt is used by default but the option is, again, ultimately up to the user regardless. I'm not "holding hands," I'm just making a precaution for dealing with nonsensical weirdos.

seqfault commented on 2023-06-23 18:32 (UTC)

@OdinVex: I'm sorry, I still don't understand hwo can I use latest PKGBUILD with src dir with successfully built engine inside. is there a possibility to do this without editing the PKGBUILD? I don't know PKGBUILD syntax, so I'm trying to avoid that, not counting variable changes (false -> true)

OdinVex commented on 2023-06-23 18:26 (UTC) (edited on 2023-06-23 18:31 (UTC) by OdinVex)

@Neko-san You shouldn't prevent people from running as root, even if it would break things. sudo means do as I say, no matter what. If their actions break something then they are at fault. Either the user installs Steam and has access to Steam-related functionality for Unreal Engine or they don't, their choice. Unreal does require the old symlink, BUT simply installing Steam like they will fix that itself. Steam manages it. It is a standard to use /opt, users should modify their own clone if they're going out of their way to change the directory. Besides, they can always run the Version Selector with -register to have UE fix the .desktop files.

@k1gen Won't work. You're about to put a nail through your foot, honestly. It's due to the order of operations. It hasn't been packaged yet, so it'll try from the beginning all over again. -i is for install, AFTER it is packaged.

seqfault commented on 2023-06-23 18:25 (UTC)

@Neko-san: what do you think about my issue? can I just git pull the PKGBUILD in yay .cache dir? if I run makepkg -i afterwards, will it keep the src directory or delete it?

Neko-san commented on 2023-06-23 18:21 (UTC)

I pushed a fix for the symlink; and the bash file exists to stop stubborn people who try to run everything as root and to make sure specific paths exists to avoid arbitrary legacy compatibility issues. It also assists with user-chosen custom install locations.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 81 Next › Last »