No, this pacakge builds openmw master , currently 0.49 .
The part of the version before the r is based on tags existing in the upstream repo and there won't be a 0.49 tag until 0.49 is branched off and master becomes 0.50 .
If you want to verify the version used, check the commit hash (leave out the g) at the end of pkgver .
There was a discussion about the version & tags in comments not long ago (check 1 and 2 pages back) but this is bwrsandman' package and they prefer using tags created by upstream.
Pinned Comments
Lone_Wolf commented on 2022-06-17 10:07 (UTC)
openmw-git has been found to require a sizable amount of temporary space during building.
The available amount depends on system specifics so is different for all systems. In case build fails with "no space left on device" you may be bitten by this.
See https://bbs.archlinux.org/viewtopic.php?id=277304 for details and possible solutions.
bwrsandman commented on 2016-09-24 14:59 (UTC) (edited on 2018-11-22 17:28 (UTC) by bwrsandman)
Please refrain from flagging the git version as out date when a new release comes out. The git aur packages update their version on install time based on the tags of the git repo.
Keep in mind that this is a VCS package and it is meant to be in line with the latest master which might not always work. It is not meant to follow the release pattern in any particularly smart way and assumes that upstream maintains their tags consistently.
For the newest release, the correct page is https://www.archlinux.org/packages/?q=openmw