Package Details: unreal-engine 5.4.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: 73
Popularity: 0.087362
First Submitted: 2016-05-01 18:37 (UTC)
Last Updated: 2024-04-24 02:23 (UTC)

Required by (1)

Sources (5)

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 2 3 4 5 6 7 8 9 10 11 .. 79 Next › Last »

OdinVex commented on 2023-06-23 19:55 (UTC)

@k1gen You forgot to add a return for prepare() too, it should be the first line...that way it isn't touched. Do the same to prepare() that you did for build(). :)

seqfault commented on 2023-06-23 19:46 (UTC)

@OdinVex: for the last twelve hours everything was building, as I started the second build before Neko-san fixed the icon issue. now that everything built fine with old PKGBUILD, I edited it to include icon fix and add return in build(). can you please check the PKGBUILD, does it look fine? I'm worried about rm -rf "$(pkgname)" on line 150: http://ix.io/4yVF

OdinVex commented on 2023-06-23 19:32 (UTC)

@k1gen Bit confused by what you mean about second build finishing and 'now try to edit'. o_O You're welcome.

seqfault commented on 2023-06-23 19:31 (UTC)

@OdinVex: thank you very much, again. I will now try to edit the PKGBUILD, as the second build just finished

OdinVex commented on 2023-06-23 19:20 (UTC) (edited on 2023-06-23 19:21 (UTC) by OdinVex)

@k1gen When the next version comes out, it's safe to just uninstall UE and clean the cache, then install normally. This was just a one-time oof. ;) In the future, it is pretty much safe to always use yay, but for big packages or things that take a long time, just clone the AUR (and subscribe for version updates) and use makepkg -si. By the way, when you use makepkg for this stuff, yay detects that too and will appropriately see it, so there isn't conflict. (But again, it currently thinks your build is old simply because of the commit pushes. Just wait to mass update with yay until after unreal-engine gets a version bump. :))

Neko-san commented on 2023-06-23 19:06 (UTC) (edited on 2023-06-23 19:06 (UTC) by Neko-san)

@k1gen I'm not going to be here this weekend to update the PKGBUILD for 5.3 but you can simply change the pkgver value to 5.3, rebuild, and you'll be good

seqfault commented on 2023-06-23 19:04 (UTC)

@OdinVex: yeah, I'll probably ditch yay soon, gotta start doing aur things on my own, this package showed me that. (I hope) last question: how do I synchronize this PKGBUILD with upstream? for example: 5.3 comes out tomorrow, how do I upgrade without wrecking unreal's cache? just clone https://aur.archlinux.org/unreal-engine.git and makepkg -si?

OdinVex commented on 2023-06-23 18:52 (UTC) (edited on 2023-06-23 18:53 (UTC) by OdinVex)

@k1gen Good luck, hopefully this goes smoothly for you. Maybe look up some resources on bash scripting and such, it's pretty much a requirement to use anything on Linux. Edit: Don't run a yay for unreal-engine until the next real update or yay will overwrite and wreck unreal-engine's cache.

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.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 79 Next › Last »