* 0.4.8 (08-06-2005)
- added second tutorial mission
- transporters can now be loaded before leaving a shop/transporter
- repairs now cost 1 instead of 0.5 xp per recruit
- Hovercraft can no longer cross forest tiles
- fixed unitposition trigger when used with shops
- extended unitdestroyed trigger to support unit classes
- hex hit testing is now pixel-perfect
- added desktop file
on all platforms supported by libtool.
* Remove the unnecessary dependencies on glut and perl, and only use
perl as a build dependency.
* Use REPLACE_PERL instead of hand-crafted substitution code.
Bump the PKGREVISION for graphics/OpenRM to 2. Due to the changed
dependency graph, bump the PKGREVISION for packages that use the OpenRM
libraries. In this case, games/genecys-client is the only one, so
bump its PKGREVISION to 2.
"-mcpu=<cpu>" into the compiler options. This should allow this
package to build on platforms that GCC does not yet recognize as a
cpu-type for which it can optimize, e.g "x86_64".
target (man.0), use 'all' which works (at least) under NetBSD and Linux.
(The problem is that the manpage suffix changes across systems.)
While here, remove a directory emptied during deinstallation.
Bump PKGREVISION to 2 due to this.
This change together with recent rillig@'s fixes close PR pkg/29493.
Liquid War is a unique multiplayer wargame. Its rules are truly
original and have been invented by Thomas Colcombet. You control
an army of liquid and have to try and eat your opponents. A single
player mode is available, but the game is definitely designed to
be multiplayer, and has network support.
USE_TOOLS and any of "autoconf", "autoconf213", "automake" or
"automake14". Also, we don't need to call the auto* tools via
${ACLOCAL}, ${AUTOCONF}, etc., since the tools framework takes care
to symlink the correct tool to the correct name, so we can just use
aclocal, autoconf, etc.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
