Mercurial > pidgin.yaz
comparison README @ 5714:f9fb9c989246
[gaim-migrate @ 6135]
Tim Ringenbach updated the readme some
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Tue, 03 Jun 2003 15:36:07 +0000 |
parents | d93f3e15381f |
children | 06e1fd7b56df |
comparison
equal
deleted
inserted
replaced
5713:def92be89b97 | 5714:f9fb9c989246 |
---|---|
22 | 22 |
23 In order to compile Gaim, you need to have GTK+ 2.0 installed (as | 23 In order to compile Gaim, you need to have GTK+ 2.0 installed (as |
24 well as the development files!). The configure script will fail if you | 24 well as the development files!). The configure script will fail if you |
25 don't. You can get it from http://www.gtk.org/. | 25 don't. You can get it from http://www.gtk.org/. |
26 | 26 |
27 Gaim will try to compile with Gnome features if you have Gnome on your | 27 For sound support, you also need libao |
28 system. If you don't have them, it will settle for simply GTK. If you | 28 (http://freshmeat.net/projects/libao/) and libaudiofile |
29 don't want Gnome bits, ./configure --disable-gnome | 29 (http://www.68k.org/~michael/audiofile/). For spellchecking support, you |
30 | 30 need libgtkspell (http://gtkspell.sf.net/). Your distro of choice |
31 If you want to build as a GNOME applet: | 31 probably already includes these, just be sure to install the development |
32 ./configure --enable-panel ; make | 32 packages. |
33 then su to root and run "make install". | |
34 Afterwards panel->Add applet->Network->Gaim should be there. | |
35 | |
36 | 33 |
37 RUN | 34 RUN |
38 === | 35 === |
39 | 36 |
40 You should run 'make install' as root to make sure plugins and other files | 37 You should run 'make install' as root to make sure plugins and other files |
41 get installed into locations they want to be in. Once you've done that, | 38 get installed into locations they want to be in. Once you've done that, |
42 you only need to run 'gaim'. | 39 you only need to run 'gaim'. |
43 | 40 |
44 To use the other services (such as Yahoo and IRC) which are available | 41 Protocol plugins (prpls) are now automaticly loaded. Simply to go the |
45 as plugins: | 42 account editor, add a new account, and all supported protocols will be |
46 | 43 there. Be sure to use OSCAR (AIM/ICQ) and not the old TOC or ICQ plugins. |
47 They are installed in $libdir/gaim, which usually is either /usr/lib/gaim | |
48 or /usr/local/lib/gaim, and should have a somewhat descriptive name (e.g. | |
49 libyahoo.so or libirc.so). Load those plugins using the normal plugin | |
50 dialog. Then in the account editor, add a new account; the Protocol option | |
51 menu should now have another option for the protocol that you loaded. Then | |
52 you can sign that account on. | |
53 | 44 |
54 Read below for protocol-specific information. | 45 Read below for protocol-specific information. |
55 | 46 |
56 | 47 |
57 PLUGINS | 48 PLUGINS |
80 make sure to put double-quotes around the "%s", otherwise bad things may | 71 make sure to put double-quotes around the "%s", otherwise bad things may |
81 happen. | 72 happen. |
82 | 73 |
83 If you come across a bug, please report it to http://gaim.sf.net/bug.php. | 74 If you come across a bug, please report it to http://gaim.sf.net/bug.php. |
84 | 75 |
85 There always seems to be some iffy-ness by a lot of people about | 76 See README.CVS for information on the bleeding edge CVS version of Gaim. |
86 whether to use the CVS version or stick with a stable release. Use the | 77 You probably shouldn't use it, as it may eat your children, as well as |
87 CVS version. If you need a version that you know is reliable, then keep | 78 your settings. |
88 your favorite one in case of an emergency. But for the most part, gaim | |
89 is not mission-critical software, and if you can help us find a few bugs | |
90 before we release, all the better. (Also, CVS tends to be more stable | |
91 than releases, since we get 10 or 12 bug reports right after we make a | |
92 release, and all those bugs are fixed within a day or two usually.) Read | |
93 http://gaim.sf.net/cvs.php for more information. | |
94 | 79 |
95 | 80 |
96 PROTOCOL INFORMATION | 81 PROTOCOL INFORMATION |
97 ==================== | 82 ==================== |
98 | 83 |