1. Erik Southworth
  2. Steam Boiler


Steam Boiler /

Filename Size Date modified Message
40 B
2.3 KB
44 B
34.3 KB
1.1 KB
692 B
4.0 KB
34 B
1.8 KB
2.2 KB
1.5 KB
Steam Boiler

.. contents::


Boiler is a script that wraps the steam program. As an alias for the
the steam command, that any authorized user can access, Boiler provides
convenient extensions and a flexible command-line interface. Install once;
run anywhere. That's how it's supposed to be.


1.) Boiler requires only a single installation per host or site. It can
    be easily used from /usr or /usr/local and still maintains the ability
    to accept self-updates, even while owned by root (no SUID required).

2.) No more having to place steam into every server base directory. If
    envoked with an explicit directory option argument, Boiler will
    automatically create symlinks to represent a steam instance where
    usually needed.

3.) The command-line interface is shorter and more flexible. If careful
    to order the arguments, an update command can be as simple as
    ``steam update tf``.


A GNU/Linux system or compatible is needed.

There is nothing to compile, so no compilers are needed.

        * HldsUpdateTool(Steam)
        * coreutils
        * util-linux

        - abi: ELF32(SysV x86)
        - soname: ELF32/libc.so.6(SysV x86)
        - soname: ELF32/libdl.so.2(SysV x86)
        - soname: ELF32/libm.so.6(SysV x86)
        - soname: ELF32/libpthread.so.0(SysV x86)
    * uncompress(gzip)
    * tar


Installing is done by the following three commands::

    $ ./configure
    $ make
    # make install (as root)

The default ``configure`` uses ``--prefix=/usr/local`` and this works fine.
Run ``./configure``, with some options if you wish. The standard options
are documented in the INSTALL file. The most interesting ones are
the usual ``--prefix=/usr``.

For more configuration details run::

    $ ./configure --help

If there are any errors during configuration, check your build environment
and try to find the error, otherwise file a bug-report on the issue tracker
or contact one of the authors.

These files will be installed.

    * ${bindir}/boiler
    * ${bindir}/steam -> ${bindir}/boiler (symlink)
    * ${pkgdatadir}/hldsupdatetool
    * ${mandir}/man1/steam.1
    * ${mandir}/man1/boiler.1


To run ``steam`` just type on a console::

    $ steam -command CMD [-game NAME] [-dir PATH] [options]

There are a few command line options. See the manual page or run for details::

    $ steam

Otherwise to run ``boiler`` just type on a console::

    $ boiler <cmd> [game] [directory] [options]

There are a few command line options. See the manual page or run for details::

    $ boiler --help

Or look into the documention in the doc/ directory.

Mostly, ``boiler`` is intended to be an alias for the ``steam`` command so, the preferred
usage would be as follows::

    $ steam <cmd> [game] [directory] [options]

And so on...You get the idea.


Boiler is distributed under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 3 of the License,
or (at your option) any later version. A copy of the license can be found in
the file COPYING included with the source code of the program. If not, see

The HldsUpdateTool(Steam) application (found in the subdirectory
hldsupdatetool/) has its own license, which can be found in the file LICENSE
included with the program.

Ideas, questions, patches and bug reports

Home page:

Primary distribution point:

Ideas, questions, patches and bug reports:

If you add something, or fix a bug, please send a patch (in 'diff -u'
format) to the issue tracker or one of the authors listed below.

------------ -----   -----       ----       ---       --         -
Erik Southworth, 2009 (s6v)