This is terrible, Brian.  I hate you already.

Tested and works great.  Probably too good.  I fear I now have to
fight my girlfriend over access to my workstation.

Now, back to my theme park...

Cheers,

Paul

On Mon, Jun 26, 2017 at 05:07:29PM -0400, Brian Callahan wrote:
| Hi ports --
| 
| Attached is a new port, games/openrct2. OpenRCT2 is an open source
| re-implementation of RollerCoaster Tycoon 2 (and the original RollerCoaster
| Tycoon).
| 
| ---
| pkg/DESCR:
| OpenRCT2 is an open source re-implementation of RollerCoaster Tycoon 2
| and the original RollerCoaster Tycoon, construction and management
| simulation games that simulate amusement park management. You can also
| build your own roller coasters.
| 
| OpenRCT2 requires game files from RollerCoaster Tycoon 2 in order to
| work properly. It will also use files from the original RollerCoaster
| Tycoon if available.
| ---
| 
| OpenRCT2 brings a lot of new features to the games, very notably full screen
| support and multiplayer.
| It does however require the original game files to play. When you launch
| openrct2 for the first time, it will tell you how to edit
| ~/.config/OpenRCT2/config.ini in order for it to find the game files (in
| short: RCT2 path goes in game_path and RCT1 path, if you have/want it, goes
| in rct1_path).
| 
| Upstream has been great in getting all the support for OpenBSD into their
| tree and test running it on their own systems (so I have reports of the game
| working on machines other than mine). I'm hosting a tarball for now but we
| will switch to their tarballs once a new release of OpenRCT2 is made.
| 
| Portcheck complains about finding hardcoded paths on this line in the port
| Makefile:
| sed -i 's,/usr/local,${TRUEPREFIX},g'
| ${WRKSRC}/src/openrct2/platform/linux.c
| but that must be a false positive.
| 
| Works well on amd64.
| 
| OK?
| 
| ~Brian
| 



-- 
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
                 http://www.weirdnet.nl/                 

Reply via email to