| tUpdate stable release number - vaccinewars - be a doctor and try to vaccinate the world |
| git clone git://src.adamsgaard.dk/vaccinewars |
| Log |
| Files |
| Refs |
| README |
| LICENSE |
| --- |
| commit ec250b0a740aaeed26fe86a16481c548e7f8799b |
| parent fdfed750468cc5f871daae642ca72d0c7182f826 |
| Author: Ben Webb |
| Date: Sun, 6 Dec 2020 11:56:53 -0800
Update stable release number
Diffstat:
M ChangeLog | 2 +-
M NEWS | 7 ++++---
M README.md | 12 ++++++------
M doc/index.html | 4 ++--
M doc/installation.html | 22 +++++++++++-----------
M doc/windows.html | 2 +-
6 files changed, 25 insertions(+), 24 deletions(-)
--- |
| diff --git a/ChangeLog b/ChangeLog |
| t@@ -1,4 +1,4 @@
-SVN
+1.6.0 06-12-2020
- Fixes to build with OpenWRT (thanks to Theodor-Iulian Ciobanu).
- Write server pidfile after fork (thanks to Theodor-Iulian Ciobanu).
- Updated German and French Canadian translations from Benjamin Karaca |
| diff --git a/NEWS b/NEWS |
| t@@ -1,6 +1,7 @@
-30th December 2005
- dopewars-1.5.12 released. This really fixes the potential exploit against
-the Windows server, which was not correctly fixed in 1.5.11.
+6th December 2020
+ dopewars-1.6.0 released. The metaserver, broken since SourceForge moved
+to HTTPS, should work again. This release also adds support for modern 64-bit
+operating systems, and newer software libraries such as GTK+3 and SDL 2.
30th December 2005
dopewars-1.5.11 released. This is largely a security bugfix release, |
| diff --git a/README.md b/README.md |
| t@@ -1,15 +1,15 @@
[![Build Status](https://travis-ci.com/benmwebb/dopewars.svg?branch=develop)](https://travis-ci.com/benmwebb/dopewars)
-This is dopewars 1.5.12, a game simulating the life of a drug dealer in
+This is dopewars 1.6.0, a game simulating the life of a drug dealer in
New York. The aim of the game is to make lots and lots of money...
unfortunately, you start the game with a hefty debt, accumulating interest,
and the cops take a rather dim view of drug dealing...
These are brief instructions; see the HTML documentation for full information.
-dopewars 1.5.12 servers should handle clients as old as version 1.4.3 with
+dopewars 1.6.0 servers should handle clients as old as version 1.4.3 with
hardly any visible problems (the reverse is also true). However, it is
-recommended that both clients and servers are upgraded to 1.5.12!
+recommended that both clients and servers are upgraded to 1.6.0!
## Installation
t@@ -19,10 +19,10 @@ Either...
Or...
-1. Get the tarball `dopewars-1.5.12.tar.gz` from the same URL
-2. Extract it via `tar -xvzf dopewars-1.5.12.tar.gz`
+1. Get the tarball `dopewars-1.6.0.tar.gz` from the same URL
+2. Extract it via `tar -xvzf dopewars-1.6.0.tar.gz`
3. Follow the instructions in the `INSTALL` file in the newly-created
- `dopewars-1.5.12` directory
+ `dopewars-1.6.0` directory
Once you're done, you can safely delete the RPM, tarball and dopewars
directory. The dopewars binary is all you need! |
| diff --git a/doc/index.html b/doc/index.html |
| t@@ -12,11 +12,11 @@ col.linklist { width: 35% }
td.linklist { vertical-align: top }
-->
-dopewars 1.5.12: Main Index
+dopewars 1.6.0: Main Index
-dopewars 1.5.12: Main Index
+dopewars 1.6.0: Main Index
| diff --git a/doc/installation.html b/doc/installation.html | | t@@ -56,8 +56,8 @@ crash with mysterious segmentation faults due to library conflicts.
- Download the
-
-i386 (Intel) RPM with your web browser.
+
+x86_64 (64-bit Intel for RedHat Enterprise 7) RPM with your web browser.
- Become root on your Unix box (if you cannot become root, then you will
probably not be able to use RPM installation, depending on how "rpm" is set
t@@ -65,7 +65,7 @@ up).
- Change to the directory containing the dopewars rpm, and install it with
the command
-rpm -Uvh dopewars-1.5.12-1.i386.rpm This will replace any
+rpm -Uvh dopewars-1.6.0-1.el7.x86_64.rpm This will replace any
already-installed earlier version.
t@@ -77,13 +77,13 @@ building the binaries from it on your system.
- Download the
-
+
source code RPM.
- Become root and change to the directory containing the new rpm.
- Build a binary rpm with the command
-rpmbuild --rebuild dopewars-1.5.12-1.src.rpm
+rpmbuild --rebuild dopewars-1.6.0-1.el7.src.rpm
- Change to the directory which the binary rpm has been written to (check
the output of the above - usually /usr/src/redhat/RPMS/xxx, where
t@@ -91,7 +91,7 @@ the output of the above - usually /usr/src/redhat/RPMS/xxx, where
"alpha" on Alphas, "x86_64" on AMD64 or EM64T machines)
- Install the binary rpm with the command
-rpm -Uvh dopewars-1.5.12-1.xxx.rpm
+rpm -Uvh dopewars-1.6.0-1.el7.xxx.rpm
t@@ -109,15 +109,15 @@ build page for more information.
- Download the
-
+
source code tarball.
- Change to the directory containing the tarball and extract the contents
with the command
-tar -xvzf dopewars-1.5.12.tar.gz
+tar -xvzf dopewars-1.6.0.tar.gz
(or similar).
-- Change into the dopewars-1.5.12 directory, and read all the important
+
- Change into the dopewars-1.6.0 directory, and read all the important
documentation in there ;) Most notably, the INSTALL file gives more details
on setup and installation.
t@@ -130,7 +130,7 @@ on setup and installation.
The configure script will test your system and set up dopewars so that it
should compile cleanly. The configure script supports a number of
configurable options; for more details, read the INSTALL file in the
-dopewars-1.5.12 directory.
+dopewars-1.6.0 directory.
If you cannot become root, run the configure script specifying directories
for which you have write access for the dopewars files, with a command
t@@ -143,7 +143,7 @@ such as
- Main index
- Last update: 05-12-2020
+ Last update: 06-12-2020
Valid XHTML 1.1
| | diff --git a/doc/windows.html b/doc/windows.html | | t@@ -40,7 +40,7 @@ the same name in the AppData directory.
the -N flag. One way to set this up is to use the
sc create utility from a command prompt, e.g.
-sc create dopewars binpath= "C:\Program Files\dopewars-1.5.12\dopewars.exe -N"
+sc create dopewars binpath= "C:\Program Files\dopewars-1.6.0\dopewars.exe -N"
Note that this will run dopewars as the Local System user, so will look for
high score/config files (and create a log file) in the corresponding AppData |
|