Package Details: openmw-git 0.41.0.1240.g0e648222b-1

Git Clone URL: https://aur.archlinux.org/openmw-git.git (read-only)
Package Base: openmw-git
Description: An open-source engine reimplementation for the role-playing game Morrowind.
Upstream URL: http://www.openmw.org
Licenses: custom, GPL3, MIT
Conflicts: openmw
Provides: openmw
Submitter: None
Maintainer: bwrsandman
Last Packager: bwrsandman
Votes: 26
Popularity: 0.000059
First Submitted: 2011-01-05 16:17
Last Updated: 2017-09-22 13:40

Pinned Comments

bwrsandman commented on 2016-09-24 14:59

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

Latest Comments

1 2 3 4 5 Next › Last »

Rulatir commented on 2018-11-22 17:31

OK, I just rebuilt after hardcoding #branch=openmw-45 (which is what I really wanted, I didn't want the master branch) and the package built as openmw-git-0.43.0.1680.g03437b712-1-x86_64.pkg.tar.xz. However the 03437b712... commit is indeed the one at the top of the openmw-45 branch as of right now, so I am satisfied with your explanation.

bwrsandman commented on 2018-11-22 17:17

TLDR: The package still rebuilds latest master as it is intended to, which is much more up to date than release 0.44. Error is due to the fact that the 0.44 tag was never merged into master and the standard way of determining versions is broken for this version only.

@Rulatir if you're looking for the 0.44 release please refer to the community version [1]

This package (openmw-git) does not guarentee to be inline with the latest release (last updated on June 20th).

It does, however guarantee to be inline with the latest master of the git repo, which as of writing this is the case (4098a7be1dac0f674171864e78ee1ab10a8d24ce Wed Nov 21 20:24:11 2018 +0100).

The reason why building it gives a misleading version number is the command in pkgver(): git describe --always

The way git describe works is by looking for the latest tag on the branch (master), taking that and giving the number of commits since that tag and a shortref.

The reason why this release is showing up as 0.43 right now is that the folks at openmw never merged the 0.44 tag into master.

Now, I could go against the AUR packaging standards[2] and hard code 0.44 in pkgver(), but I think we can agree that this would cause more issues down the line such as when 0.45 is released. Not to mention this sort of package update forces a half hour to multi hour rebuild for all users using aur helpers.

VCS packages, unfortunately, are not an exact science and they require upstream to do things consistently.

[1] https://www.archlinux.org/packages/community/x86_64/openmw/

[2] https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function

Rulatir commented on 2018-11-22 16:53

@bwrsandman The cold fact is that there is a release 0.44, but this package builds version 0.43 as of today. Automatic selection of the newest release seems to fail in this case, and manual intervention by maintainer is needed after all. I am therefore flagging the package as outdated.

ase1590 commented on 2018-11-19 01:32

https://gitlab.com/OpenMW/openmw/issues/4692

Until this bug is resolved, OpenMW will need to require OpenSceneGraph 3.4.1

bwrsandman commented on 2016-09-24 14:59

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

esclapion commented on 2016-09-04 10:12

Release 0.4 is out

RedComet commented on 2016-07-19 15:30

I took a look at the /usr/local/lib folder and it sseems that awhile back. I tried to compile ffmpeg from source when I was very new to arch and didn't properly uninstall it. I removed the files from the previous build reinstalled ffmpeg and everything works fine now.

bwrsandman commented on 2016-07-18 11:42

@RedComet I've tested and the build isn't broken per say.

It's strange that you're linking with /usr/local/lib/libavcodec.a, I am not sure where that's coming from, you should be linking with /usr/lib/libavcodec.so

Could you check with pacman -Qo /usr/local/lib/libavcodec.a and see where it comes from?

RedComet commented on 2016-07-17 12:46

I get this error:

[ 47%] Building CXX object apps/openmw/CMakeFiles/openmw.dir/crashcatcher.cpp.o
[ 47%] Linking CXX executable ../../openmw
/usr/bin/ld: /usr/local/lib/libavcodec.a(lclenc.o): undefined reference to symbol 'deflateReset'
/usr/lib/libz.so.1: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [apps/openmw/CMakeFiles/openmw.dir/build.make:6358: openmw] Error 1
make[1]: *** [CMakeFiles/Makefile2:502: apps/openmw/CMakeFiles/openmw.dir/all] Error 2

darkbasic commented on 2016-05-12 14:54

https://forum.openmw.org/viewtopic.php?f=8&t=3544

It's fixed now.