This package does not install the run_uh.py script.
Search Criteria
Package Details: unknown-horizons-git 2017.2.373.g8319a4773-1
| Git Clone URL: | https://aur.archlinux.org/unknown-horizons-git.git (read-only) |
|---|---|
| Package Base: | unknown-horizons-git |
| Description: | Open source real-time strategy game with the comfy Anno1602 feeling. |
| Upstream URL: | http://www.unknown-horizons.org |
| Licenses: | |
| Conflicts: | |
| Replaces: | |
| Submitter: | nihathrael |
| Maintainer: | LinuxDonald |
| Last Packager: | LinuxDonald |
| Votes: | 50 |
| Popularity: | 0.056696 |
| First Submitted: | 2010-08-26 10:53 |
| Last Updated: | 2017-04-19 21:11 |
Dependencies (7)
- fife-git
- python
- python-future
- python-pillow (python-pillow-simd)
- python-yaml
- git (git-git) (make)
- intltool (make)
Required by (0)
Sources (1)
Latest Comments
ChrisOelmueller commented on 2017-08-03 17:29
Anonymous comment on 2017-08-03 15:53
balduin commented on 2014-09-27 13:28
Works without any problems.
ChrisOelmueller commented on 2014-08-22 14:09
And migrated back to fife-git after the segfaults look like they've been fixed.
ChrisOelmueller commented on 2014-08-19 12:52
Thanks! Updated to fife in lieu of fife-git for stability concerns mentioned before.
arcanis commented on 2014-08-19 05:18
please update dependency list according to the request [1]:
fife-svn -> fife-git
1. https://mailman.archlinux.org/pipermail/aur-requests/2014-August/001181.html
hagabaka commented on 2014-04-13 01:38
@ChrisOelmueller The svn repository fife-svn uses seems to be last updated around Feburary 2013. What issues do you see with fife-git?
ChrisOelmueller commented on 2014-04-12 23:32
Probably can work with fife-git as well, but there are several things about it (and fifechan-git) that I'm not confident with requiring right now.
Herk commented on 2014-04-12 20:58
Shouldn't this depend on fife-git instead of fife-svn?
hagabaka commented on 2013-09-30 03:46
The lines in pkgver() and package():
cd "$pkgdir/${pkgname%-*}"
should be replaced with:
cd "$srcdir/${pkgname%-*}"
As opposed to…? All I'm aware of is UH installing a symlink to that exact launcher under a name that's easier to memorize.
If something is expected to be placed elsewhere during setup process I'd assume the best course of action is asking about a change in that process upstream – the package simply trusts those definitions are correct and executes them. But I didn't understand the expected behavior from your comment just yet, so you might have to clarify a bit: What would you like to happen but didn't?