New makedep qt5-tools needed since https://gitlab.com/OpenMW/openmw/-/commit/7e345436f4104676a6ade618f1720b42aaeaa5bd
Please add it.
Git Clone URL: | https://aur.archlinux.org/openmw-git.git (read-only, click to copy) |
---|---|
Package Base: | openmw-git |
Description: | An open-source engine reimplementation for the role-playing game Morrowind. |
Upstream URL: | http://www.openmw.org |
Licenses: | custom, MIT, GPL-3.0-or-later |
Conflicts: | openmw |
Provides: | openmw |
Submitter: | None |
Maintainer: | bwrsandman (Lone_Wolf) |
Last Packager: | Lone_Wolf |
Votes: | 30 |
Popularity: | 0.000018 |
First Submitted: | 2011-01-05 16:17 (UTC) |
Last Updated: | 2024-06-25 12:42 (UTC) |
New makedep qt5-tools needed since https://gitlab.com/OpenMW/openmw/-/commit/7e345436f4104676a6ade618f1720b42aaeaa5bd
Please add it.
@bwrsandman :
As mnetioned in the bug report I uploaded https://aur.archlinux.org/packages/mygui-openmw to provide mygui 3.4.3 for this package.
Please change mygui to mygui-openmw in dependencies.
confirmed, archlinux mygui package needs to be updated to 3.4.3 .
@S3ctor could you share what error you get so I can see if it's the packaging or the source code.
Currently the package does not build as of commit 6a87ba8f333481636359c5cd250ed14f0b3108e7, I pinned my PKGBUILD to ac9cfc782a613663d6f8440a4a06bc3119fcabc9 and it worked.
@rtentser Thanks for bringing this up.
The inconsistent tag versioning of openmw has given me a lot of trouble and I haven't always been able to keep up or grep the version correctly.
This instance was a bug in my latest change to the package.
To avoid this in the future, I have noted the most common cases of failure with the tag and added a validation test in comments of the pkgver
function so future fixes don't regress:
First we strip off any openmw-*
There must be no dashes.
We remove any other words such as rc
Finally, if there is no major or patch number, add 0
Test using this script:
declare -a test_tags=("openmw-0.29.0" "0.42.0" "0.42.1" "1.42.1" "0.47.0-RC3" "openmw-48-rc10")
for _tag in "${test_tags[@]}"; do
_fixed_tag=$(echo $_tag | sed 's/^openmw-//' | sed 's/-.*//' | sed -E 's/^([0-9]+)$/0.\1.0/')
echo "$_tag -> $_fixed_tag"
done
Expected output:
openmw-0.29.0 -> 0.29.0
0.42.0 -> 0.42.0
0.42.1 -> 0.42.1
1.42.1 -> 1.42.1
0.47.0-RC3 -> 0.47.0
openmw-48-rc10 -> 0.48.0
For some reason this package sets incorrect version (0.0.48.0.0.r3001.g518aa5c6ae-1 for example) and always wants to update (because 0.0.48 is less than 0.48)
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.
Thanks for the quick update, but there's one more problem. This is not the latest build of OpenMW.. The latest .is 0.49.This 0.48. You can grab binary versions of OpenMW .0.49.0 here (the official OpenMW uses it for their build releases).. https://redfortune.de/openmw/nightly/
The PKGBUILD won't compile due to an pkgver error It needs to be fixed ==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: 48-rc12.1.r2533.gb383efabf5
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