The SSH host key has changed on 8 April, 2022 to this one: SHA256:573uTBSeh74kvOo0HJXi5ijdzRm8me27suzNEDlGyrQ

Released v1

v1
Gergely Polonkai 6 years ago
commit 980af5458a
  1. 4
      ChangeLog
  2. 182
      INSTALL
  3. 51
      Makefile.in
  4. 91
      README
  5. 23
      TODO
  6. 165
      config.h.in
  7. 110
      configure.in
  8. 33
      create_source_htmls
  9. 46
      data/Makefile.in
  10. 11
      data/botcommander.desktop.in.in
  11. 154
      data/botcommander.schemas.in
  12. 6
      debian/README.Debian
  13. 10
      debian/botcommander-default.ex
  14. 22
      debian/botcommander.doc-base.EX
  15. 6
      debian/changelog
  16. 1
      debian/compat
  17. 14
      debian/control
  18. 14
      debian/copyright
  19. 4
      debian/cron.d.ex
  20. 2
      debian/dirs
  21. 1
      debian/docs
  22. 45
      debian/emacsen-install.ex
  23. 15
      debian/emacsen-remove.ex
  24. 25
      debian/emacsen-startup.ex
  25. 74
      debian/init.d.ex
  26. 59
      debian/manpage.1.ex
  27. 156
      debian/manpage.sgml.ex
  28. 148
      debian/manpage.xml.ex
  29. 2
      debian/menu.ex
  30. 42
      debian/postinst.ex
  31. 38
      debian/postrm.ex
  32. 38
      debian/preinst.ex
  33. 38
      debian/prerm.ex
  34. 107
      debian/rules
  35. 22
      debian/watch.ex
  36. 31
      doc/Makefile.in
  37. 349
      doc/botcommander.texinfo
  38. 542
      doc/botcommander.xml
  39. 2
      doc/version.texinfo
  40. 50
      eggdrop/botcommander.tcl
  41. 9
      gentoo/net-misc/botcommander/ChangeLog
  42. 16
      gentoo/net-misc/botcommander/Manifest
  43. 34
      gentoo/net-misc/botcommander/botcommander-1.0.ebuild
  44. 3
      gentoo/net-misc/botcommander/files/digest-botcommander-1.0
  45. 8
      gentoo/net-misc/botcommander/metadata.xml
  46. 76
      include/defines.h
  47. 161
      include/functions.h
  48. 187
      include/typedefs.h
  49. 63
      include/variables.h
  50. 16
      pixmaps/Makefile.in
  51. BIN
      pixmaps/bc48.png
  52. BIN
      pixmaps/bc48_trans.png
  53. 307
      po/BotCommander.pot
  54. 221
      po/Makefile.in.in
  55. 13
      po/POTFILES.in
  56. 324
      po/hu.po
  57. 9
      rules.in
  58. 33
      src/Makefile.in
  59. 91
      src/about.c
  60. 532
      src/botlist.c
  61. 270
      src/bots.c
  62. 518
      src/callbacks.c
  63. 138
      src/chanprops.c
  64. 453
      src/commands.c
  65. 611
      src/config.c
  66. 69
      src/debug.c
  67. 123
      src/history.c
  68. 143
      src/main.c
  69. 116
      src/networking.c
  70. 366
      src/setup.c
  71. 244
      src/string.c
  72. 677
      src/tabs.c
  73. 412
      src/widgets.c
  74. 26
      template

@ -0,0 +1,4 @@
2007-04-09 19:41 Gergely Polonkai <polesz@botcommander.hu>
* Added this ChangeLog file.

@ -0,0 +1,182 @@
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.ac' is used to create `configure' by a program
called `autoconf'. You only need `configure.ac' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.

@ -0,0 +1,51 @@
include rules
subdirs = src doc pixmaps po data
SHELL = /bin/sh
srcdir = @srcdir@
all:
@for dir in ${subdirs}; do \
(cd $$dir && $(MAKE) all) \
|| case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
install:
@for dir in ${subdirs}; do \
(cd $$dir && $(MAKE) install) \
|| case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
clean:
/bin/rm -f *~
@for dir in ${subdirs}; do \
(cd $$dir && $(MAKE) clean) \
|| case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
distclean:
@for dir in ${subdirs}; do \
(cd $$dir && $(MAKE) distclean) \
|| case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
/bin/rm -f Makefile config.h config.status config.cache config.log intltool-extract intltool-merge intltool-update rules configure aclocal.m4
/bin/rm -rf autom4te.cache/
# automatic re-running of configure if the configure.in file has changed
${srcdir}/configure: configure.in aclocal.m4
cd ${srcdir} && autoconf
# autoheader might not change config.h.in, so touch a stamp file
${srcdir}/config.h.in: stamp-h.in
${srcdir}/stamp-h.in: configure.in aclocal.m4
cd ${srcdir} && autoheader
echo timestamp > ${srcdir}/stamp-h.in
config.h: stamp-h
stamp-h: config.h.in config.status
./config.status
Makefile: Makefile.in config.status
./config.status
config.status: configure
./config.status --recheck

@ -0,0 +1,91 @@
This short document is originally based on eggdrop's README file.
Contents
0. Important notice
1. What is BotCommander
2. How do I get BotCommander?
3. Quick startup
4. Frequently Asked Questions
5. Legal stuff
6. Documentation
7. Obtaining help
_________________________________________________________________
(0) NOTICE
Please read this document, and the original BotCommander documentation
before asking for help! These files contain almost everything possible, and
are always growing, as people ask me more and more questions.
_________________________________________________________________
(1) WHAT IS BOTCOMMANDER?
BotCommander is a customisable telnet client, heavily specialized with the
usage with Eggdrop IRC bots. Currently it possesses only the planned basic
functionality, but I have many-many plans, such as module-writing,
scripting and such.
BotCommander is continously updated: bugs are getting fixed, and new
features are being added, which sometimes can cause new bugs. Currently
there is a so called "stable" version out there, but there are still known
bugs.
_________________________________________________________________
(2) HOW DO I GET BOTCOMMANDER?
Before you can install/compile BotCommander, you will need several other
software installed on your machine.
As BotCommander currently depends heavily on GTK+ 2 and Gnome 2, you will
need these. If you are planning (or must) install BotCommander from
sources, you will also need the development libraries of them. These
software comes with most of the Linux/Unix distributions, so the only thing
you may have to do is to install them.
The current stable version (as of writing) is 1.0; you can download it
(amongst many other files) from http://www.botcommander.hu/.
Optionally, you can get the latest SVN version from
http://www.botcommander.hu/files/botcommander-svn.tar.bz2. BUT BEWARE! This
version may contain code snippets which will never compile on any machine!
This is because I'm a nasty developer, and sometimes upload this kind of
code, so I can continue coding on my other machine after an svn update. I'm
also planning to add anonymous SVN access, but currently I don't have
enough knowledge about SVN to do such thing.
_________________________________________________________________
(3) QUICK STARTUP
About installation quick-start you should read the INSTALL file; about
usage, you should go and read the original BotCommander documentation. The
latter is written in DocBook XML, and is compiled into a PDF document upon
a successful installation. It can be found in the doc/ directory.
_________________________________________________________________
(4) FREQUENTLY ASKED QUESTIONS
_________________________________________________________________
(5) LEGAL STUFF
_________________________________________________________________
(6) DOCUMENTATION
_________________________________________________________________
(7) OBTAINING HELP

23
TODO

@ -0,0 +1,23 @@
* Preferences
- Save recalled command at the end of history?
- Save command to history which is already there somewhere?
* Bot list
- Edit Save in conf backend
* Command completion
* If there is a command which can be abbreviated and one
which can not, get_command_from_abbrev() should return the former.
* User should be able to set local vhost to use.
* (Channel and Handle list) hideable.
* Create a status icon.
* BotCommander SWITCH command. This will act like the CONNECT command, but it will connect in a new tab. If the specified bot is already connected in one of the tabs, BotCommander will switch to that tab instead of opening a new one.
* Contents of aclocal.m4 can be splitted somehow. But where to?
* http://www.botcommander.hu/files/botcommander-latest.tar.bz2 <= http://www.botcommander.hu/latest

@ -0,0 +1,165 @@
/* vim: set foldmethod=marker : */
/* {{{ Legal info
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Library General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
}}} */
/* {{{ Author and file info
* config.h.in
*
* Wed Nov 09 22:16:59 2005
* Copyright (C) 2005 Gergely POLONKAI
* polesz@techinfo.hu
*
* This file holds some default settings.
}}} */
/* This is the GConf path where BC stores it's settings. You should leave this
* as the default */
#define GCONF2_ROOT "/apps/botcommander"
/* {{{ Default settings */
#define DEFAULT_SCROLL_ON_OUTPUT TRUE
#define DEFAULT_CHANGE_TO_MESSAGE TRUE
#define DEFAULT_DEBUG FALSE
#define DEFAULT_TRANSPARENT_BACKGROUND FALSE
#define DEFAULT_BACKGROUND_SATURATION 1.0
#define DEFAULT_DEFAULT_MODE "B"
#define DEFAULT_VTE_FONT "Courier 10 Pitch 12"
#define DEFAULT_CHANGE_TO_NEW_TAB FALSE
#define DEFAULT_HISTORY_LENGTH 100
/* }}} */
/* Eggdrop itself uses ISO-8859-1 when using the default english language. You
* only have to change this if you use a different language file (e.g hungarian
* is usually in ISO-8859-2), or you use a script or module which sends out
* characters in a different character set. */
#define BOT_CHARSET "ISO-8859-1"
#define MAX_READ_LINE_LEN 1024
/* config.h.in. Most of this file is generated from configure.in by
* autoheader. */
/* Define to 1 if you have the <fcntl.h> header file. */
#undef HAVE_FCNTL_H
/* GETTEXT package name */
#undef GETTEXT_PACKAGE
/* Define to 1 if you have the `gethostbyname' function. */
#undef HAVE_GETHOSTBYNAME
/* Define to 1 if you have the <inttypes.h> header file. */
#undef HAVE_INTTYPES_H
/* Define to 1 if you have the <libintl.h> header file. */
#undef HAVE_LIBINTL_H
/* Define to 1 if you have the `m' library (-lm). */
#undef HAVE_LIBM
/* Define to 1 if you have the <locale.h> header file. */
#undef HAVE_LOCALE_H
/* Define to 1 if your system has a GNU libc compatible `malloc' function, and
to 0 otherwise. */
#undef HAVE_MALLOC
/* Define to 1 if you have the <memory.h> header file. */
#undef HAVE_MEMORY_H
/* Define to 1 if you have the `memset' function. */
#undef HAVE_MEMSET
/* Define to 1 if you have the <netdb.h> header file. */
#undef HAVE_NETDB_H
/* Define to 1 if you have the <netinet/in.h> header file. */
#undef HAVE_NETINET_IN_H
/* Define to 1 if you have the `setlocale' function. */
#undef HAVE_SETLOCALE
/* Define to 1 if you have the `socket' function. */
#undef HAVE_SOCKET
/* Define to 1 if you have the <stdint.h> header file. */
#undef HAVE_STDINT_H
/* Define to 1 if you have the <stdlib.h> header file. */
#undef HAVE_STDLIB_H
/* Define to 1 if you have the `strchr' function. */
#undef HAVE_STRCHR
/* Define to 1 if you have the `strerror' function. */
#undef HAVE_STRERROR
/* Define to 1 if you have the <strings.h> header file. */
#undef HAVE_STRINGS_H
/* Define to 1 if you have the <string.h> header file. */
#undef HAVE_STRING_H
/* Define to 1 if you have the `strtol' function. */
#undef HAVE_STRTOL
/* Define to 1 if you have the <sys/socket.h> header file. */
#undef HAVE_SYS_SOCKET_H
/* Define to 1 if you have the <sys/stat.h> header file. */
#undef HAVE_SYS_STAT_H
/* Define to 1 if you have the <sys/types.h> header file. */
#undef HAVE_SYS_TYPES_H
/* Define to 1 if you have the <unistd.h> header file. */
#undef HAVE_UNISTD_H
/* Define to the address where bug reports for this package should be sent. */
#undef PACKAGE_BUGREPORT
/* Define to the full name of this package. */
#undef PACKAGE_NAME
/* Define to the full name and version of this package. */
#undef PACKAGE_STRING
/* Define to the one symbol short name of this package. */
#undef PACKAGE_TARNAME
/* Define to the version of this package. */
#undef PACKAGE_VERSION
/* Define as the return type of signal handlers (`int' or `void'). */
#undef RETSIGTYPE
/* Define to 1 if you have the ANSI C header files. */
#undef STDC_HEADERS
/* Define to empty if `const' does not conform to ANSI C. */
#undef const
/* Define to rpl_malloc if the replacement function should be used. */
#undef malloc
/* Define to `int' if <sys/types.h> does not define. */
#undef ssize_t
/* Package pixmaps directory */
#undef PACKAGE_PIXMAPS_DIR
/* Package local directory */
#undef PACKAGE_LOCALE_DIR

@ -0,0 +1,110 @@
AC_PREREQ(2.60)
AC_INIT(BotCommander, 1.0, polesz@botcommander.hu)
AM_INIT_AUTOMAKE
PACKAGE=botcommander
BOTCOMMANDER_VERSION=1.0
ALL_LINGUAS=hu
GETTEXT_PACKAGE=botcommander
GLIB_REQUIRED=2.0.6
GDK_PIXBUF_REQUIRED=2.0.0
GTK_REQUIRED=2.2.0
GNOME_REQUIRED=2.0.2
GNOME_UI_REQUIRED=2.0.2
VTE_REQUIRED=0.9.0
AC_GNU_SOURCE
AM_GNU_GETTEXT
AM_GLIB_GNU_GETTEXT
AC_SUBST(GLIB_REQUIRED)
AC_SUBST(GDK_PIXBUF_REQUIRED)
AC_SUBST(GTK_REQUIRED)
AC_SUBST(GNOME_REQUIRED)
AC_SUBST(GNOME_UI_REQUIRED)
AC_SUBST(VTE_REQUIRED)
AC_SUBST(GETTEXT_PACKAGE)
AC_SUBST(PACKAGE)
AC_DEFINE_UNQUOTED(GETTEXT_PACKAGE,"$GETTEXT_PACKAGE", [GETTEXT package name])
if test "x${prefix}" = "xNONE"; then
packageprefix=${ac_default_prefix}
else
packageprefix=${prefix}
fi
if test "x${prefix}" = "xNONE"; then
AC_DEFINE_UNQUOTED(PACKAGE_LOCALE_DIR, "${ac_default_prefix}/${DATADIRNAME}/locale", [Package local directory])
else
AC_DEFINE_UNQUOTED(PACKAGE_LOCALE_DIR, "${prefix}/${DATADIRNAME}/locale", [Package local directory])
fi
packagepixmapsdir=share/pixmaps/${PACKAGE}
PACKAGE_PIXMAPS_DIR="${packageprefix}/${packagepixmapsdir}"
AC_SUBST(PACKAGE_PIXMAPS_DIR)
AC_DEFINE_UNQUOTED(PACKAGE_PIXMAPS_DIR, "${packageprefix}/${packagepixmapsdir}", [Package pixmaps directory])
AC_CONFIG_HEADER([config.h])
AC_ARG_ENABLE(debug, [ --enable-debug Enable debug mode], CFLAGS="$CFLAGS -DDEBUG -g -Wall")
dnl Check for required programs
AC_PROG_CC
AC_PROG_CPP
AC_PROG_INSTALL
IT_PROG_INTLTOOL
AC_CHECK_PROGS([TEXI2PDF], [texi2pdf])
dnl Check for extensions
AC_OBJEXT
AC_EXEEXT
dnl Check for math library
AC_CHECK_LIB([m], [exp10])
AC_ISC_POSIX
# Checks for header files.
AC_HEADER_STDC
AC_CHECK_HEADERS([fcntl.h libintl.h locale.h netdb.h netinet/in.h stdlib.h string.h sys/socket.h unistd.h])
# Checks for typedefs, structures, and compiler characteristics.
AC_C_CONST
AC_TYPE_SSIZE_T
# Checks for library functions.
AC_FUNC_MALLOC
AC_TYPE_SIGNAL
AC_CHECK_FUNCS([gethostbyname memset setlocale socket strchr strerror strtol])
PKG_PROG_PKG_CONFIG([0.9.0])
if test x$PKG_CONFIG = xno; then
AC_MSG_ERROR(Please install the pkg-config package!);
fi
PKG_CHECK_MODULES(BOTCOMMANDER, glib-2.0 >= $GLIB_REQUIRED gtk+-2.0 >= $GTK_REQUIRED libgnome-2.0 >= $GNOME_REQUIRED libgnomeui-2.0 >= $GNOME_REQUIRED vte >= $VTE_REQUIRED gconf-2.0)
AC_SUBST(BOTCOMMANDER_CFLAGS)
AC_SUBST(BOTCOMMANDER_LIBS)
AM_GCONF_SOURCE_2
AC_PATH_PROG([GCONFTOOL], [gconftool-2], [no])
if test "x$GCONFTOOL" = "xno"; then
AC_MSG_ERROR([gconftool-2 executable not found in your path - should be installed with GConf])
fi
AC_CONFIG_FILES([rules
Makefile
data/Makefile
doc/Makefile
src/Makefile
pixmaps/Makefile
po/Makefile.in
data/botcommander.desktop.in
data/botcommander.schemas])
AC_OUTPUT

@ -0,0 +1,33 @@
#! /bin/sh
MAIN_DIR=source_html
C2HTML=`which c2html`
if [ x$C2HTML = x ]
then
echo "c2html not found. Please install that first!"
exit 1
fi
rm -rf $MAIN_DIR
mkdir -p $MAIN_DIR
echo "<html>
<head>
<title>BotCommander sources in HTML</title>
</head>
<body>
<h1>BotCommander sources in HTML</h1>" >> $MAIN_DIR/index.html
for FILE in `find -name \*.[ch]`
do
DIR=`dirname $FILE`
mkdir -p $MAIN_DIR/$DIR
cat $FILE | c2html > $MAIN_DIR/$FILE.html
echo " <a href=\"$FILE.html\">$FILE</a><br />" >> $MAIN_DIR/index.html
done
echo " </body>
</html>" >> $MAIN_DIR/index.html
exit 0

@ -0,0 +1,46 @@
include ../rules
GCONFTOOL = @GCONFTOOL@
top_srcdir = @top_srcdir@
top_builddir = @top_builddir@
sysconfdir = @sysconfdir@
datarootdir = @datarootdir@
datadir = @datadir@
INTLTOOL_MERGE = @INTLTOOL_MERGE@
INTLTOOL_DESKTOP_RULE = @INTLTOOL_DESKTOP_RULE@
INTLTOOL_SCHEMAS_RULE = @INTLTOOL_SCHEMAS_RULE@
GCONF_SCHEMA_FILE_DIR = @GCONF_SCHEMA_FILE_DIR@
GCONF_SCHEMAS_INSTALL_TRUE = @GCONF_SCHEMAS_INSTALL_TRUE@
GCONF_SCHEMA_CONFIG_SOURCE = @GCONF_SCHEMA_CONFIG_SOURCE@
gnomemenudir = $(datadir)/applications
gnomemenu_premerge_file = botcommander.desktop.in
gnomemenu_DATA = $(gnomemenu_premerge_file:.desktop.in=.desktop)
schema_in_files = botcommander.schemas.in
schemadir = $(GCONF_SCHEMA_FILE_DIR)
schema_DATA = $(schema_in_files:.schemas.in=.schemas)
all: $(gnomemenu_DATA)
clean:
install: $(gnomemenu_DATA)
@GCONF_SCHEMAS_INSTALL_TRUE@ if test -z "$(DESTDIR)" ; then \
@GCONF_SCHEMAS_INSTALL_TRUE@ for p in $(schema_DATA) ; do \
@GCONF_SCHEMAS_INSTALL_TRUE@ GCONF_CONFIG_SOURCE=$(GCONF_SCHEMA_CONFIG_SOURCE) $(GCONFTOOL) --makefile-install-rule $(top_builddir)/data/$$p >&1 > /dev/null; \
@GCONF_SCHEMAS_INSTALL_TRUE@ done \
@GCONF_SCHEMAS_INSTALL_TRUE@ fi
$(top_srcdir)/mkinstalldirs $(gnomemenudir)
$(top_srcdir)/mkinstalldirs $(schemadir)
$(INSTALL) -m 0644 $(gnomemenu_DATA) $(gnomemenudir)
$(INSTALL) -m 0644 $(schema_DATA) $(schemadir)
distclean:
rm -f botcommander.desktop botcommander.desktop.in botcommander.schemas Makefile
@INTLTOOL_DESKTOP_RULE@
@INTLTOOL_SCHEMAS_RULE@

@ -0,0 +1,11 @@
[Desktop Entry]
_Name=BotCommander
_Comment=BotCommander eggdrop client
Exec=botcommander
Icon=@PACKAGE_PIXMAPS_DIR@/bc48_trans.png
Terminal=false
X-MultipleArgs=false
Type=Application
Categories=Application;Network;
Encoding=UTF-8
StartupNotify=true

@ -0,0 +1,154 @@
<gconfschemafile>
<schemalist>
<schema>
<key>/schemas/apps/botcommander/background_saturation</key>
<applyto>/apps/botcommander/background_saturation</applyto>
<owner>botcommander</owner>
<type>float</type>
<default>0.0</default>
<locale name="C">
<short>Background is not opaque by default</short>
<long>background_saturation only has effect when transparent_background is true. If so, this value gives the opacity of the VTE</long>
</locale>
<locale name="hu">
<short>A háttér alapértelmezés szerint nem áttetsző</short>
<long>A background_saturation értékét csak akkor veszi figyelembe a program, ha a transparent_background értéke true. Ha így van, ez az érték adja meg a VTE áttetszőségének mértékét.</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/change_to_message</key>
<applyto>/apps/botcommander/change_to_message</applyto>
<owner>botcommander</owner>
<type>bool</type>
<default>true</default>
<locale name="C">
<short>By default, BotCommander will change to Message mode after connecting to a bot</short>
<long>When this option is true, BotCommander will set Message mode after connecting to a bot</long>
</locale>
<locale name="hu">
<short>Alapértelmezés szerint a BotCommander átvált Üzenet módba miután csatlakozott egy bothoz</short>
<long>Ha ez az opció true, a BotCommander átvált Üzenet módba, miután csatlakozott egy bothoz</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/change_to_new_tab</key>
<applyto>/apps/botcommander/change_to_new_tab</applyto>
<owner>botcommander</owner>
<type>bool</type>
<default>true</default>
<locale name="C">
<short>BotCommander changes to the newly created tab by default</short>
<long>When this value is true, BotCommander will change to the newly opened tab. Otherwise, the new tab won't be activated</long>
</locale>
<locale name="hu">
<short>A BotCommander alapértelmezés szerint átvált az újonnan létrehozott fülre</short>
<long>Ha ez az érték true, a BotCommander automatikusan átvált az újonnan megnyitott fülre. Ha nem, a fül nem lesz aktiválva</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/debug</key>
<applyto>/apps/botcommander/debug</applyto>
<owner>botcommander</owner>
<type>bool</type>
<default>false</default>
<locale name="C">
<short>By default, BotCommander won't print out debug messages</short>
<long>If this option is true, and the code is compiled with the DEBUG flag, BotCommander will print debug messages</long>
</locale>
<locale name="hu">
<short>Alapértelmezés szerint a BotCommander nem fogja kiírni a hibakereső üzeneteket</short>
<long>Ha ez az opció be van kapcsolva, és a kód a DEBUG opcióval lett fordítva, a BotCommander folyamatosan kiírja a hibakereső üzeneteket</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/default_mode</key>
<applyto>/apps/botcommander/default_mode</applyto>
<owner>botcommander</owner>
<type>string</type>
<default>B</default>
<locale name="C">
<short>By default, BotCommander will use BotCommander command mode</short>
<long>When you open a new tab, BotCommander will use this mod as the initial mode of the tab</long>
</locale>
<locale name="hu">
<short>Alapértelmezés szerint a BotCommander Botcommander Parancs-módot használ</short>
<long>Mikor megnyitsz egy új fület, a BotCommander ezt a módot állítja be rajta</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/history_length</key>
<applyto>/apps/botcommander/history_length</applyto>
<owner>botcommander</owner>
<type>int</type>
<default>300</default>
<locale name="C">
<short>The default scrollback-size for the VTEs is 300 lines</short>
<long>The VTEs scrollback is set to this value</long>
</locale>
<locale name="hu">
<short>A VTE-k memóritára alapértelmezésben 300 sor</short>
<long>A VTE-k memóriatárának mérete ennyi sorra van állítva</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/sanity</key>
<applyto>/apps/botcommander/sanity</applyto>
<owner>botcommander</owner>
<type>string</type>
<default>Needed for gconf sanity check, please don't remove!</default>
<locale name="C">
<short>NEVER CHANGE THIS VALUE!</short>
<long>NEVER CHANGE THIS VALUE! This is for sanity check. Maybe I'll remove it soon. NEVER CHANGE THIS VALUE!</long>
</locale>
<locale name="hu">
<short>SOHA NE VÁLTOZTASD MEG EZT AZ ÉRTÉKET!</short>
<long>SOHA NE VÁLTOZTASD MEG EZT AZ ÉRTÉKET! Ez a gconf ellenőrzésére szolgál. Valószínűleg hamarosan törlöm. SOHA NE VÁLTOZTAST MEG EZT AZ ÉRTÉKET!</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/scroll_on_output</key>
<applyto>/apps/botcommander/scroll_on_output</applyto>
<owner>botcommander</owner>
<type>bool</type>
<default>true</default>
<locale name="C">
<short>By default, BotCommander will scroll the contents of the VTE when new data arrives from the bot</short>
<long>When this option is true, BotCommander will automatically scroll to the bottom of the window when a new line arrives from the bot</long>
</locale>
<locale name="hu">
<short>Alapértelmezés szerint a BotCommander a VTE aljára görget, ha új adat érkezik a bottól</short>
<long>Ha ez az opció true, a BotCommander automatikusan a VTE aljára görget, ha új adat érkezik a bottól</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/transparent_background</key>
<applyto>/apps/botcommander/transparent_background</applyto>
<owner>botcommander</owner>
<type>bool</type>
<default>false</default>
<locale name="C">
<short>By default, the VTEs' background is not transparent</short>
<long>If you set this option to true, and background_saturation to a number greater then 0, the VTEs' background will be opaque</long>
</locale>
<locale name="hu">
<short>Alapértelmezés szerint a VTE-k háttere nem áttetsző</short>
<long>Ha ezt az értéket true-ra állítod, a background_saturation értékét pedig 0-nál nagyobbra, a VTE-k háttere áttetsző lesz</long>
</locale>
</schema>
<schema>
<key>/schemas/apps/botcommander/vte_font</key>
<applyto>/apps/botcommander/vte_font</applyto>
<owner>botcommander</owner>
<type>string</type>
<default>Courier 10 Pitch 12</default>
<locale name="C">
<short>By default, the VTEs use the Courier 10 Pitch font with a 12pt size</short>
<long>The VTEs' font will set to this value</long>
</locale>
<locale name="hu">
<short>Alapértelmezés szerint a VTE-k a Courier 10 Pitch font 12pt méretű változatát használják</short>
<long>Ez az érték lesz megadva, mint a VTE-k betűkészlete</long>
</locale>
</schema>
</schemalist>
</gconfschemafile>

@ -0,0 +1,6 @@
botcommander for Debian
-----------------------
<possible notes regarding this package - if none, delete this file>
-- Gergely POLONKAI <polesz@botcommander.hu>, Mon, 11 Sep 2006 07:31:20 +0200

@ -0,0 +1,10 @@
# Defaults for botcommander initscript
# sourced by /etc/init.d/botcommander
# installed at /etc/default/botcommander by the maintainer scripts
#
# This is a POSIX shell fragment
#
# Additional options that are passed to the Daemon.
DAEMON_OPTS=""

@ -0,0 +1,22 @@
Document: botcommander
Title: Debian botcommander Manual
Author: Gergely POLONKAI (polesz@botcommander.hu)
Abstract: This manual describes what botcommander is
and how it can be used to
manage online manuals on Debian systems.
Section: utils
Format: debiandoc-sgml
Files: /usr/share/doc/botcommander/botcommander.sgml.gz
Format: postscript
Files: /usr/share/doc/botcommander/botcommander.ps.gz
Format: text
Files: /usr/share/doc/botcommander/botcommander.text.gz
Format: HTML
Index: /usr/share/doc/botcommander/html/index.html
Files: /usr/share/doc/botcommander/html/*.html

6
debian/changelog vendored

@ -0,0 +1,6 @@
botcommander (1.0-1) unstable; urgency=low
* Initial release (Closes: #nnnn) <nnnn is the bug number of your ITP>
-- POLONKAI Gergely <polesz@botcommander.hu> Mon, 11 Sep 2006 07:41:46 +0200

1
debian/compat vendored

@ -0,0 +1 @@
5

14
debian/control vendored

@ -0,0 +1,14 @@
Source: botcommander
Section: utils
Priority: optional
Maintainer: Gergely POLONKAI <polesz@botcommander.hu>
Build-Depends: debhelper (>= 5), autotools-dev, libgnomeui-0, libvte4, libgtk2.0-0, libgconf2-4
Standards-Version: 3.7.2
Package: botcommander
Architecture: i386
Depends: ${shlibs:Depends}
Description: BotCommander is a graphical eggdrop client for UN*X sytems
BotCommander is a graphical eggdrop client written for UN*X systems. This is
still a work-in-progress, as it already functional. There are still many plans
which are not implemented yet.

14
debian/copyright vendored

@ -0,0 +1,14 @@
This package was debianized by Gergely POLONKAI <polesz@botcommander.hu> on
Mon, 11 Sep 2006 07:31:20 +0200.
It was downloaded from http://www.botcommander.hu/
Upstream Author: Gergely POLONKAI <polesz@botcommander.hu>
Copyright: Gergely POLONKAI, 2006
License: GNU GPL, version 2 or later
The Debian packaging is (C) 2006, Gergely POLONKAI <polesz@botcommander.hu> and
is licensed under the GPL, see `/usr/share/common-licenses/GPL'.

4
debian/cron.d.ex vendored

@ -0,0 +1,4 @@
#
# Regular cron jobs for the botcommander package
#
0 4 * * * root botcommander_maintenance

2
debian/dirs vendored

@ -0,0 +1,2 @@
usr/bin
usr/share/pixmaps/botcommander

1
debian/docs vendored

@ -0,0 +1 @@
TODO

@ -0,0 +1,45 @@
#! /bin/sh -e
# /usr/lib/emacsen-common/packages/install/botcommander
# Written by Jim Van Zandt <jrv@debian.org>, borrowing heavily
# from the install scripts for gettext by Santiago Vila
# <sanvila@ctv.es> and octave by Dirk Eddelbuettel <edd@debian.org>.
FLAVOR=$1
PACKAGE=botcommander
if [ ${FLAVOR} = emacs ]; then exit 0; fi
echo install/${PACKAGE}: Handling install for emacsen flavor ${FLAVOR}
#FLAVORTEST=`echo $FLAVOR | cut -c-6`
#if [ ${FLAVORTEST} = xemacs ] ; then
# SITEFLAG="-no-site-file"
#else
# SITEFLAG="--no-site-file"
#fi
FLAGS="${SITEFLAG} -q -batch -l path.el -f batch-byte-compile"
ELDIR=/usr/share/emacs/site-lisp/${PACKAGE}
ELCDIR=/usr/share/${FLAVOR}/site-lisp/${PACKAGE}
# Install-info-altdir does not actually exist.
# Maybe somebody will write it.
if test -x /usr/sbin/install-info-altdir; then
echo install/${PACKAGE}: install Info links for ${FLAVOR}
install-info-altdir --quiet --section "" "" --dirname=${FLAVOR} /usr/info/${PACKAGE}.info.gz
fi
install -m 755 -d ${ELCDIR}
cd ${ELDIR}
FILES=`echo *.el`
cp ${FILES} ${ELCDIR}
cd ${ELCDIR}
cat << EOF > path.el
(setq load-path (cons "." load-path) byte-compile-warnings nil)
EOF
${FLAVOR} ${FLAGS} ${FILES}
rm -f *.el path.el
exit 0

@ -0,0 +1,15 @@
#!/bin/sh -e
# /usr/lib/emacsen-common/packages/remove/botcommander
FLAVOR=$1
PACKAGE=botcommander
if [ ${FLAVOR} != emacs ]; then
if test -x /usr/sbin/install-info-altdir; then
echo remove/${PACKAGE}: removing Info links for ${FLAVOR}
install-info-altdir --quiet --remove --dirname=${FLAVOR} /usr/info/botcommander.info.gz
fi
echo remove/${PACKAGE}: purging byte-compiled files for ${FLAVOR}
rm -rf /usr/share/${FLAVOR}/site-lisp/${PACKAGE}
fi

@ -0,0 +1,25 @@
;; -*-emacs-lisp-*-
;;
;; Emacs startup file, e.g. /etc/emacs/site-start.d/50botcommander.el
;; for the Debian botcommander package
;;
;; Originally contributed by Nils Naumann <naumann@unileoben.ac.at>
;; Modified by Dirk Eddelbuettel <edd@debian.org>
;; Adapted for dh-make by Jim Van Zandt <jrv@debian.org>
;; The botcommander package follows the Debian/GNU Linux 'emacsen' policy and
;; byte-compiles its elisp files for each 'emacs flavor' (emacs19,
;; xemacs19, emacs20, xemacs20...). The compiled code is then
;; installed in a subdirectory of the respective site-lisp directory.
;; We have to add this to the load-path:
(let ((package-dir (concat "/usr/share/"
(symbol-name flavor)
"/site-lisp/botcommander")))
;; If package-dir does not exist, the botcommander package must have
;; removed but not purged, and we should skip the setup.
(when (file-directory-p package-dir)
(setq load-path (cons package-dir load-path))
(autoload 'botcommander-mode "botcommander-mode"
"Major mode for editing botcommander files." t)
(add-to-list 'auto-mode-alist '("\\.botcommander$" . botcommander-mode))))

74
debian/init.d.ex vendored

@ -0,0 +1,74 @@
#! /bin/sh
#
# skeleton example file to build /etc/init.d/ scripts.
# This file should be used to construct scripts for /etc/init.d.
#
# Written by Miquel van Smoorenburg <miquels@cistron.nl>.
# Modified for Debian
# by Ian Murdock <imurdock@gnu.ai.mit.edu>.
#
# Version: @(#)skeleton 1.9 26-Feb-2001 miquels@cistron.nl
#
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/botcommander
NAME=botcommander
DESC=botcommander
test -x $DAEMON || exit 0
# Include botcommander defaults if available
if [ -f /etc/default/botcommander ] ; then
. /etc/default/botcommander
fi
set -e
case "$1" in
start)
echo -n "Starting $DESC: "
start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $DAEMON_OPTS
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
start-stop-daemon --stop --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON
echo "$NAME."
;;
#reload)
#
# If the daemon can reload its config files on the fly
# for example by sending it SIGHUP, do it here.
#
# If the daemon responds to changes in its config file
# directly anyway, make this a do-nothing entry.
#
# echo "Reloading $DESC configuration files."
# start-stop-daemon --stop --signal 1 --quiet --pidfile \
# /var/run/$NAME.pid --exec $DAEMON
#;;
restart|force-reload)
#
# If the "reload" option is implemented, move the "force-reload"
# option to the "reload" entry above. If not, "force-reload" is
# just the same as "restart".
#
echo -n "Restarting $DESC: "
start-stop-daemon --stop --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON
sleep 1
start-stop-daemon --start --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON -- $DAEMON_OPTS
echo "$NAME."
;;
*)
N=/etc/init.d/$NAME
# echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
exit 0

@ -0,0 +1,59 @@
.\" Hey, EMACS: -*- nroff -*-
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH BOTCOMMANDER SECTION "szeptember 11, 2006"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
.\" .nh disable hyphenation
.\" .hy enable hyphenation
.\" .ad l left justify
.\" .ad b justify to both left and right margins
.\" .nf disable filling
.\" .fi enable filling
.\" .br insert line break
.\" .sp <n> insert n+1 empty lines
.\" for manpage-specific macros, see man(7)
.SH NAME
botcommander \- program to do something
.SH SYNOPSIS
.B botcommander
.RI [ options ] " files" ...
.br
.B bar
.RI [ options ] " files" ...
.SH DESCRIPTION
This manual page documents briefly the
.B botcommander
and
.B bar
commands.
.PP
.\" TeX users may be more comfortable with the \fB<whatever>\fP and
.\" \fI<whatever>\fP escape sequences to invode bold face and italics,
.\" respectively.
\fBbotcommander\fP is a program that...
.SH OPTIONS
These programs follow the usual GNU command line syntax, with long
options starting with two dashes (`-').
A summary of options is included below.
For a complete description, see the Info files.
.TP
.B \-h, \-\-help
Show summary of options.
.TP
.B \-v, \-\-version
Show version of program.
.SH SEE ALSO
.BR bar (1),
.BR baz (1).
.br
The programs are documented fully by
.IR "The Rise and Fall of a Fooish Bar" ,
available via the Info system.
.SH AUTHOR
botcommander was written by <upstream author>.
.PP
This manual page was written by Gergely POLONKAI <polesz@botcommander.hu>,
for the Debian project (but may be used by others).

@ -0,0 +1,156 @@
<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!-- Process this file with docbook-to-man to generate an nroff manual
page: `docbook-to-man manpage.sgml > manpage.1'. You may view
the manual page with: `docbook-to-man manpage.sgml | nroff -man |
less'. A typical entry in a Makefile or Makefile.am is:
manpage.1: manpage.sgml
docbook-to-man $< > $@
The docbook-to-man binary is found in the docbook-to-man package.
Please remember that if you create the nroff version in one of the
debian/rules file targets (such as build), you will need to include
docbook-to-man in your Build-Depends control field.
-->
<!-- Fill in your name for FIRSTNAME and SURNAME. -->
<!ENTITY dhfirstname "<firstname>FIRSTNAME</firstname>">
<!ENTITY dhsurname "<surname>SURNAME</surname>">
<!-- Please adjust the date whenever revising the manpage. -->
<!ENTITY dhdate "<date>szeptember 11, 2006</date>">
<!-- SECTION should be 1-8, maybe w/ subsection other parameters are
allowed: see man(7), man(1). -->
<!ENTITY dhsection "<manvolnum>SECTION</manvolnum>">
<!ENTITY dhemail "<email>polesz@botcommander.hu</email>">
<!ENTITY dhusername "Gergely POLONKAI">
<!ENTITY dhucpackage "<refentrytitle>BOTCOMMANDER</refentrytitle>">
<!ENTITY dhpackage "botcommander">
<!ENTITY debian "<productname>Debian</productname>">
<!ENTITY gnu "<acronym>GNU</acronym>">
<!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
]>
<refentry>
<refentryinfo>
<address>
&dhemail;
</address>
<author>
&dhfirstname;
&dhsurname;
</author>
<copyright>
<year>2003</year>
<holder>&dhusername;</holder>
</copyright>
&dhdate;
</refentryinfo>
<refmeta>
&dhucpackage;
&dhsection;
</refmeta>
<refnamediv>
<refname>&dhpackage;</refname>
<refpurpose>program to do something</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>&dhpackage;</command>
<arg><option>-e <replaceable>this</replaceable></option></arg>
<arg><option>--example <replaceable>that</replaceable></option></arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>DESCRIPTION</title>
<para>This manual page documents briefly the
<command>&dhpackage;</command> and <command>bar</command>
commands.</para>
<para>This manual page was written for the &debian; distribution
because the original program does not have a manual page.
Instead, it has documentation in the &gnu;
<application>Info</application> format; see below.</para>
<para><command>&dhpackage;</command> is a program that...</para>
</refsect1>
<refsect1>
<title>OPTIONS</title>
<para>These programs follow the usual &gnu; command line syntax,
with long options starting with two dashes (`-'). A summary of
options is included below. For a complete description, see the
<application>Info</application> files.</para>
<variablelist>
<varlistentry>
<term><option>-h</option>
<option>--help</option>
</term>
<listitem>
<para>Show summary of options.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-v</option>
<option>--version</option>
</term>
<listitem>
<para>Show version of program.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para>bar (1), baz (1).</para>
<para>The programs are documented fully by <citetitle>The Rise and
Fall of a Fooish Bar</citetitle> available via the
<application>Info</application> system.</para>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>This manual page was written by &dhusername; &dhemail; for
the &debian; system (but may be used by others). Permission is
granted to copy, distribute and/or modify this document under
the terms of the &gnu; General Public License, Version 2 any
later version published by the Free Software Foundation.
</para>
<para>
On Debian systems, the complete text of the GNU General Public
License can be found in /usr/share/common-licenses/GPL.
</para>
</refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->

@ -0,0 +1,148 @@
<?xml version='1.0' encoding='ISO-8859-1'?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!--
Process this file with an XSLT processor: `xsltproc \
-''-nonet /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/\
manpages/docbook.xsl manpage.dbk'. A manual page
<package>.<section> will be generated. You may view the
manual page with: nroff -man <package>.<section> | less'. A
typical entry in a Makefile or Makefile.am is:
DB2MAN=/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/\
manpages/docbook.xsl
XP=xsltproc -''-nonet
manpage.1: manpage.dbk
$(XP) $(DB2MAN) $<
The xsltproc binary is found in the xsltproc package. The
XSL files are in docbook-xsl. Please remember that if you
create the nroff version in one of the debian/rules file
targets (such as build), you will need to include xsltproc
and docbook-xsl in your Build-Depends control field.
-->
<!-- Fill in your name for FIRSTNAME and SURNAME. -->
<!ENTITY dhfirstname "<firstname>FIRSTNAME</firstname>">
<!ENTITY dhsurname "<surname>SURNAME</surname>">
<!-- Please adjust the date whenever revising the manpage. -->
<!ENTITY dhdate "<date>szeptember 11, 2006</date>">
<!-- SECTION should be 1-8, maybe w/ subsection other parameters are
allowed: see man(7), man(1). -->
<!ENTITY dhsection "<manvolnum>SECTION</manvolnum>">
<!ENTITY dhemail "<email>polesz@botcommander.hu</email>">
<!ENTITY dhusername "Gergely POLONKAI">
<!ENTITY dhucpackage "<refentrytitle>BOTCOMMANDER</refentrytitle>">
<!ENTITY dhpackage "botcommander">
<!ENTITY debian "<productname>Debian</productname>">
<!ENTITY gnu "<acronym>GNU</acronym>">
<!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
]>
<refentry>
<refentryinfo>
<address>
&dhemail;
</address>
<author>
&dhfirstname;
&dhsurname;
</author>
<copyright>
<year>2003</year>
<holder>&dhusername;</holder>
</copyright>
&dhdate;
</refentryinfo>
<refmeta>
&dhucpackage;
&dhsection;
</refmeta>
<refnamediv>
<refname>&dhpackage;</refname>
<refpurpose>program to do something</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>&dhpackage;</command>
<arg><option>-e <replaceable>this</replaceable></option></