source: branches/ithildin-1.1/README @ 855

Revision 855, 6.6 KB checked in by elly, 20 months ago (diff)

Make README more politically correct, per Ryan's request.

  • Property svn:keywords set to Id Rev
Line 
1-------------------------------------------------------------------------------
2$Id$
3-------------------------------------------------------------------------------
4[Table of Contents]:
5...0: Preface / Requirements
6...1: Getting the source
7...2: Compiling
8...3: Installing
9...4: Running
10...5: Help!  It didn't work!
11..98: Credits
12..99: Contact
13-------------------------------------------------------------------------------
14WARNING WARNING WARNING
15This software is obsolete and should be considered essentially unmaintained.
16As such, ithildin will no longer be maintained by the irc.darkmyst.org dev team.
17
18I (elly on irc.darkmyst.org) am maintaining patches to it for the near future, but
19a migration to charybdis is planned. So far as we know, no other networks use
20Ithildin, so at that point this project will be dead. If you use ithildin or
21otherwise care about it, please visit irc.darkmyst.org #dev and we'll talk about
22the future. I am only dealing with bug fixes right now; new feature development
23is halted.
24
25tl;dr: If you are using Ithildin, stop. It's broken, and it won't be fixed.
26
27[0: Preface / Requirements]:
28
29Reading READMEs from start to finish is usually a good idea.  They tend to
30contain a lot of information that is valid/valuable for 99% of users.  That
31being said, I've tried to keep things short and to the point for those of you
32who have little patience.  Before you start running the daemon, you should read
33the below list of requirements to make sure you've got everything you need.
34
35Requirements:
361. A modern Unix.  At the present time this system is not designed to run on
37   anything but Unix and Unix-variant systems.  I will be doing a win32
38   version "real soon now" unless Microsoft fires me and I go back to
39   working on Unix systems as a dayjob. :)
402. Access to a C compiler, and a few megabytes of space.  You can install this
41   system as a regular user, but you will need the compiler and space.
423. At least moderate knowledge of working with files on your system.  You're
43   going to need to know how to edit configuration files, run programs, and
44   probably move data around.  I've tried to make things fairly clear, but
45   YMMV.
464. A module which you wish to run.  The base system doesn't come with any
47   modules, you'll need to get them on your own.  There are some available
48   from the site where the base system is hosted.
495. GNU Make.  On Linux this is invariably the regular 'make' which you
50   already have.  On BSD systems (and others) it may be installed as
51   'gmake'.
52
53-------------------------------------------------------------------------------
54[1: Getting the source]:
55
56The source code for ithildin can currently be retrieved from one of two
57places: Subversion (like CVS) or the website.  If you
58
59* The website is at http://ithildin.org/dist/
60
61* The subversion repository is located at:
62  http://svn.ithildin.org/repo/trunk/ithildin
63  To check out the latest code from the svn repository, you can do:
64  $ svn co http://svn.ithildin.org/repo/trunk/ithildin
65  If you do not have subversion installed on your system it can be retrieved
66  from http://subversion.tigris.org/.  Please note that getting the svn copy
67  of the source will give you every module in the system.  You might not
68  want that.
69
70-------------------------------------------------------------------------------
71[2: Compiling]:
72
73This system should be relatively straightforward to compile.  You'll need to do
74the following:
75
761) Extract any modules you wish to use in the "modules/" directory.  For
77example let us say you downloaded the "syslog" module package in your home
78directory, you would do:
79$ cd ithildin/modules
80$ tar -zxf ~/syslog.tar.gz
81
822) If you got the source from svn, you'll need to generate a configure script.
83This is done by using the 'autoconf' command, like so:
84$ autoconf -o configure autoconf/configure.ac
85If you downloaded the source from somewhere else this step is not necessary.
86
873) Configure the system using the configure script by doing:
88$ ./configure --prefix=foo
89(you might wish to run configure with the --help option to see if you're
90interested in using any addons).  If you want to install system-wide you'll
91probably want a prefix of '/usr' or '/usr/local'.  If you want to install in
92your home directory, you'll probably want to use --prefix=/home/yourdir or
93--prefix=/home/yourdir/ithildin (to keep it separate from other stuff).
94And if you're installing in a home directory or somewhere separate from
95other system binaries/libraries you will probably want to use the
96--disable-dir-suffix option to configure.  It will keep the directory
97structure in a cleaner condition.  Also, if you've got a bunch of stuff in
98modules/ but you only want to compile some (or one) module you should do:
99$ ./configure ... --with-modules="module1 module2 module3"
100Replacing module1, etc with the names of the modules you want compiled and
101installed.
102
1034) Build the source by doing:
104$ make
105Any 'make' variant should suffice here.
106
107That's it.  If all of this went well, then you can move on to the installing
108step.  If not, see section 4.
109
110-------------------------------------------------------------------------------
111[3: Installing]:
112
113Installation is, as building, relatively simple, you should be able to install
114the system by simply doing:
115
116$ make install
117
118That's it.  If all went well, move on to the next section.  If not, see section
1194.
120
121-------------------------------------------------------------------------------
122[4: Running]:
123
124You'll probably need to configure the system before you run it.  Look in
125$prefix/etc/ithildin/ for the various configuration files.
126
127-------------------------------------------------------------------------------
128[5: Help!  It didn't work!]:
129
130Right now there is no FAQ for "it didn't work" type issues, however you are
131invited to file a defect (see the BUGS file) if you believe this is a defect
132in the product and not an error in your configuration.
133
134-------------------------------------------------------------------------------
135[98: Credits]:
136
137See the DEVELOPERS file for a list of developers who are/have been involved
138with the project.
139
140-------------------------------------------------------------------------------
141[99: Contact]:
142
143You can contact me (the maintainer) using the following details:
144
145Real life: Chip Norkus
146Email    : wd@ithildin.org
147Address  : If you really really want it just ask.
148IRC      : DALnet (occasionally): wd
149           EFnet (always on, sometimes idle): wd
150AIM      : doubleyewdee
151MSN      : wd@teleri.net
152
153Please only e-mail me if you have questions NOT answered in the documentation
154here.  Please do not e-mail me about third-party modules or things wholly
155unrelated to this project.  Thank you.
156
Note: See TracBrowser for help on using the repository browser.