variables so that the default INSTALL/DEINSTALL scripts from the
pkginstall framework do the right thing. Where possible, move some
post-install directions for package setup into MESSAGE files so that
they may be re-inspected by querying the installed package using
"pkg_info -D ...".
INSTALL/DEINSTALL script creation within pkgsrc.
If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts. If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:
INSTALL_SRC= ${PKGDIR}/INSTALL
DEINSTALL_SRC= # emtpy
As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts. By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).
In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework. The only public variables relating to the templates are:
INSTALL_SRC INSTALL_TEMPLATE
DEINSTALL_SRC DEINSTALL_TEMPLATE
HEADER_TEMPLATE
The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
TetriNET is an addictive 6 player tetr*s game
What this program does is set up a TetriNET server that ordinary
TetriNET clients can connect to. It attempts to fix some of the
"glaring" holes in the TetriNET protocol that I discovered, and which
I'm sure some people use as cheats, but I now see why it is nearly
impossible to fix ;), without a modification to the client.
I've kept the server as close to the same as the original TetriNET
server, but I've added some extras that I've often wanted, such as
the "/kick" and "/ban" keywords.
Please note this server in no way encompasses the whole game. The clients
are the ones that do most of the work, with the server just passing suitable
packets between each client, and of course adding some of its own.
Author: Brendan Grieve (brg@cheerful.com)
Packaged by David Ferlier.
