- Dokumentation ergaenzt und verbessert.
This commit is contained in:
parent
cc18008b6c
commit
194f18c8e6
13
AUTHORS
13
AUTHORS
|
@ -0,0 +1,13 @@
|
||||||
|
|
||||||
|
ngIRCd - Next Generation IRC Server
|
||||||
|
|
||||||
|
(c)2001 by Alexander Barton,
|
||||||
|
alex@barton.de, http://www.barton.de/
|
||||||
|
|
||||||
|
ngIRCd ist freie Software und steht unter
|
||||||
|
der GNU General Public License.
|
||||||
|
|
||||||
|
-- AUTHORS / Autoren --
|
||||||
|
|
||||||
|
|
||||||
|
Alexander Barton, alex@arthur.ath.cx
|
14
ChangeLog
14
ChangeLog
|
@ -0,0 +1,14 @@
|
||||||
|
|
||||||
|
ngIRCd - Next Generation IRC Server
|
||||||
|
|
||||||
|
(c)2001 by Alexander Barton,
|
||||||
|
alex@barton.de, http://www.barton.de/
|
||||||
|
|
||||||
|
ngIRCd ist freie Software und steht unter
|
||||||
|
der GNU General Public License.
|
||||||
|
|
||||||
|
-- ChangeLog / Aenderungen --
|
||||||
|
|
||||||
|
|
||||||
|
[Zur Zeit ist kein "ChangeLog" vorhanden. Bitte ziehe die CVS-Kommentare in
|
||||||
|
den einzelnen Dateien zu Rate ...]
|
197
INSTALL
197
INSTALL
|
@ -1,182 +1,75 @@
|
||||||
Basic Installation
|
|
||||||
==================
|
|
||||||
|
|
||||||
These are generic installation instructions.
|
ngIRCd - Next Generation IRC Server
|
||||||
|
|
||||||
The `configure' shell script attempts to guess correct values for
|
(c)2001 by Alexander Barton,
|
||||||
various system-dependent variables used during compilation. It uses
|
alex@barton.de, http://www.barton.de/
|
||||||
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
|
ngIRCd ist freie Software und steht unter
|
||||||
to figure out how `configure' could check whether to do them, and mail
|
der GNU General Public License.
|
||||||
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.in' is used to create `configure' by a program
|
-- INSTALL / Installation --
|
||||||
called `autoconf'. You only need `configure.in' 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
|
ngIRCd ist fuer UNIXoide-Systeme konzipiert. Dieser Text beschreibt den
|
||||||
`./configure' to configure the package for your system. If you're
|
"Standardfall": ein UNIX bzw. UNIX-aehnliches System, das von GNU automake
|
||||||
using `csh' on an old version of System V, you might need to type
|
und GNU autoconf ("configure") unterstuetzt wird.
|
||||||
`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.
|
I. Quick Start
|
||||||
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
3. Optionally, type `make check' to run any self-tests that come with
|
In der Regel sind folgende Schritte ausreichend:
|
||||||
the package.
|
|
||||||
|
|
||||||
4. Type `make install' to install the programs and any data files and
|
1) ./autogen.sh [nur erforderlich, wenn ueber CVS bezogen]
|
||||||
documentation.
|
2) ./configure
|
||||||
|
3) make
|
||||||
|
|
||||||
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
|
zu 1) autogen.sh:
|
||||||
=====================
|
|
||||||
|
|
||||||
Some systems require unusual options for compilation or linking that
|
Der erste Schritt, autogen.sh, ist nur notwendig, wenn das configure-Script
|
||||||
the `configure' script does not know about. You can give `configure'
|
noch nicht vorhanden ist. Dies ist nie bei offiziellen ("stabilen") Versionen
|
||||||
initial values for variables by setting them in the environment. Using
|
in tar.gz-Archiven der Fall, jedoch nie, wenn der Source-Code ueber CVS
|
||||||
a Bourne-compatible shell, you can do that on the command line like
|
bezogen wurde.
|
||||||
this:
|
|
||||||
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
|
|
||||||
|
|
||||||
Or on systems that have the `env' program, you can do it like this:
|
Dieser Absatz ist also eigentlich ausschliesslich fuer Entwickler interessant.
|
||||||
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
|
|
||||||
|
|
||||||
Compiling For Multiple Architectures
|
autogen.sh erzeugt die fuer das configure-Script notwendigen Makefile.in's
|
||||||
====================================
|
sowie das configure-Script selber und weitere fuer den make-Lauf erforderliche
|
||||||
|
Dateien. Dazu wird sowohl GNU automake als auch GNU autoconf (in aktuellen
|
||||||
|
Versionen!) benoetigt.
|
||||||
|
|
||||||
You can compile the package for more than one kind of computer at the
|
(nochmal: "Endanwender" mussen diesen Schritt i.d.R. nicht ausfuehren!)
|
||||||
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
|
zu 2) ./configure:
|
||||||
==================
|
|
||||||
|
|
||||||
By default, `make install' will install the package's files in
|
Mit dem configure-Script wird ngIRCd, wie GNU Software meistens, an das
|
||||||
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
lokale System angepasst und die erforderlichen Makefile's erzeugt.
|
||||||
installation prefix other than `/usr/local' by giving `configure' the
|
|
||||||
option `--prefix=PATH'.
|
|
||||||
|
|
||||||
You can specify separate installation prefixes for
|
Im Optimalfall sollte configure alle benoetigten Libraries, Header etc. selber
|
||||||
architecture-specific files and architecture-independent files. If you
|
erkennen und entsprechend reagieren. Sollte dies einmal nicht der Fall sein,
|
||||||
give `configure' the option `--exec-prefix=PATH', the package will use
|
so zeigt "./configure --help" moegliche Optionen.
|
||||||
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
|
zu 3) make:
|
||||||
with an extra prefix or suffix on their names by giving `configure' the
|
|
||||||
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
|
||||||
|
|
||||||
Optional Features
|
Der make-Befehl bearbeitet die vom configure-Script erzeugten Makefile's und
|
||||||
=================
|
uebersetzt die comBase-Library und die Testprogramme.
|
||||||
|
|
||||||
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
|
II. Nuetzliche make-Targets
|
||||||
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
|
Die vom configure-Script erzeugten Makefile's enthalten immer die folgenden
|
||||||
==========================
|
nuetzlichen Targets:
|
||||||
|
|
||||||
There may be some features `configure' can not figure out
|
- clean: alle Erzeugnisse des Compilers/Linkers loeschen.
|
||||||
automatically, but needs to determine by the type of host the package
|
Naechster Schritt: -> make
|
||||||
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
|
- distclean: zusaetzliche alle Makefile's loeschen.
|
||||||
`config.sub' isn't included in this package, then this package doesn't
|
Naechster Schritt: -> ./configure
|
||||||
need to know the host type.
|
|
||||||
|
|
||||||
If you are building compiler tools for cross-compiling, you can also
|
- maintainer-clean: alle automat. erzeugten Dateien loeschen.
|
||||||
use the `--target=TYPE' option to select the type of system they will
|
Naechster Schritt: -> ./autogen.sh
|
||||||
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.
|
|
||||||
|
|
14
NEWS
14
NEWS
|
@ -0,0 +1,14 @@
|
||||||
|
|
||||||
|
ngIRCd - Next Generation IRC Server
|
||||||
|
|
||||||
|
(c)2001 by Alexander Barton,
|
||||||
|
alex@barton.de, http://www.barton.de/
|
||||||
|
|
||||||
|
ngIRCd ist freie Software und steht unter
|
||||||
|
der GNU General Public License.
|
||||||
|
|
||||||
|
-- NEWS / Neuigkeiten --
|
||||||
|
|
||||||
|
|
||||||
|
[Zur Zeit nicht vorhanden. Bitte die CVS-Kommentare in den einzelnen Dateien
|
||||||
|
zu Rate ziehen -- oder das ChangeLog, so es existent sein sollte ;-)]
|
42
README
42
README
|
@ -0,0 +1,42 @@
|
||||||
|
|
||||||
|
ngIRCd - Next Generation IRC Server
|
||||||
|
|
||||||
|
(c)2001 by Alexander Barton,
|
||||||
|
alex@barton.de, http://www.barton.de/
|
||||||
|
|
||||||
|
ngIRCd ist freie Software und steht unter
|
||||||
|
der GNU General Public License.
|
||||||
|
|
||||||
|
-- README / Liesmich --
|
||||||
|
|
||||||
|
|
||||||
|
ngIRCd ist ein Server fuer den Internet Relay Chat (IRC). Er ist von Grund
|
||||||
|
auf neu geschrieben, also nicht wie die meisten anderen IRCd's vom Urvater,
|
||||||
|
dem Daemon des IRCNet abgeleitet.
|
||||||
|
|
||||||
|
Zur Zeit befindet sich ngIRCd noch in Entwicklung, vieles ist noch nicht
|
||||||
|
implementiert bzw. nur "halbherzig": Channels gibt es noch nicht, genau so
|
||||||
|
wenig wie Server-Links. Das private Chatten (PRIVMSG) mit den Client-Befehlen
|
||||||
|
/msg und /query sollte hingegen funktionieren, ein wenig praktische Funk-
|
||||||
|
tionalitaet ist also tatsaechlich schon vorhanden ;-)
|
||||||
|
|
||||||
|
Diese Version ist aber auf jeden Fall als "Preview" anzusehen!
|
||||||
|
|
||||||
|
Bisher (mehr oder wenig vollstaendig) implementierte IRC-Befehle:
|
||||||
|
|
||||||
|
DIE, ISON, MODE, MOTD, NAMES, NICK, NOTICE, OPER, PASS, PING, PONG, PRIVMSG,
|
||||||
|
QUIT, RESTART, USER, USERHOST, WHOIS.
|
||||||
|
|
||||||
|
Ueber Rueckmeldungen, Bug-Reports und Patches freue ich mich! Also los, haut
|
||||||
|
in die Tasten! :-))
|
||||||
|
|
||||||
|
Via E-Mail erreichst du mich als <alex@arthur.ath.cx> bzw. <alex@barton.de>.
|
||||||
|
Die Homepage des ngIRCd findest du unter <http://arthur.ath.cx/~alex/ngircd/>.
|
||||||
|
|
||||||
|
[ ... more to come ... ]
|
||||||
|
|
||||||
|
|
||||||
|
Hinweise zur Installation findest du in der Datei INSTALL.
|
||||||
|
Alle Autoren von ngIRCd sind in AUTHORS aufgefuehrt.
|
||||||
|
In der Datei COPYING steht die GNU General Public License.
|
||||||
|
Das README liest du gerade ,-)
|
21
doc/CVS.txt
21
doc/CVS.txt
|
@ -0,0 +1,21 @@
|
||||||
|
|
||||||
|
ngIRCd - Next Generation IRC Server
|
||||||
|
|
||||||
|
(c)2001 by Alexander Barton,
|
||||||
|
alex@barton.de, http://www.barton.de/
|
||||||
|
|
||||||
|
ngIRCd ist freie Software und steht unter
|
||||||
|
der GNU General Public License.
|
||||||
|
|
||||||
|
-- CVS.txt --
|
||||||
|
|
||||||
|
|
||||||
|
Die Sourcen des ngIRCd werden mit dem "Concurrent Versions System" (CVS)
|
||||||
|
verwaltet. Somit koennen ohne Probleme mehrere Leute gleichzeitig die Sourcen
|
||||||
|
bearbeitet.
|
||||||
|
|
||||||
|
Dieser Text soll in Zukunft die Grundlagen beschreiben. Tut er aber leider
|
||||||
|
noch nicht, also frage einfach Alex direkt (siehe AUTHORS-Text), wenn du
|
||||||
|
daran interessiert bist, Zugriff auf den Quellcode via CVS zu bekommen!
|
||||||
|
|
||||||
|
[ ... more to come ... ]
|
29
doc/RFC.txt
29
doc/RFC.txt
|
@ -0,0 +1,29 @@
|
||||||
|
|
||||||
|
ngIRCd - Next Generation IRC Server
|
||||||
|
|
||||||
|
(c)2001 by Alexander Barton,
|
||||||
|
alex@barton.de, http://www.barton.de/
|
||||||
|
|
||||||
|
ngIRCd ist freie Software und steht unter
|
||||||
|
der GNU General Public License.
|
||||||
|
|
||||||
|
-- RFC.txt --
|
||||||
|
|
||||||
|
|
||||||
|
Das IRC-Protokoll ist in diesen RFC's (Request For Comments) dokumentiert:
|
||||||
|
|
||||||
|
1459 Oikarinen, J. & D. Reed, "Internet Relay Chat Protocol",
|
||||||
|
May 1993, [IRC].
|
||||||
|
|
||||||
|
2810 Kalt, C., "Internet Relay Chat: Architecture",
|
||||||
|
April 2000, [IRC-ARCH].
|
||||||
|
|
||||||
|
2811 Kalt, C., "Internet Relay Chat: Channel Management",
|
||||||
|
April 2000, [IRC-CHAN].
|
||||||
|
|
||||||
|
2812 Kalt, C., "Internet Relay Chat: Client Protocol",
|
||||||
|
April 2000, [IRC-CLIENT].
|
||||||
|
|
||||||
|
2813 Kalt, C., "Internet Relay Chat: Server Protocol",
|
||||||
|
April 2000, [IRC-SERVER].
|
||||||
|
|
Loading…
Reference in New Issue