|
960
|
1 STATUS of GAIM CVS tree. Last modified $Date: 2000-10-09 20:02:02 -0400 (Mon, 09 Oct 2000) $ by $Author: warmenhoven $.
|
|
|
2
|
|
|
3 This file is meant to provide gaim users who use the CVS version to see whether
|
|
|
4 the actually want to compile what they just checked out. Gaim CVS is usually
|
|
|
5 relatively stable (we use it all the time), but has tendencies to be quirky at
|
|
|
6 times.
|
|
|
7
|
|
|
8
|
|
|
9 OVERALL
|
|
|
10 =======
|
|
|
11
|
|
|
12 The current CVS tree is completely broken. You can still use it to sign in and
|
|
|
13 converse with users as normal. If you only have one account signed in then all
|
|
|
14 of the old functions still work perfectly (or as well as they did before The
|
|
|
15 Change (multiple connections)).
|
|
|
16
|
|
|
17 There are a lot of things that are probably going to be very buggy over the
|
|
|
18 next month or so. Please bear with us.
|
|
|
19
|
|
|
20
|
|
|
21 MULTIPLE CONNECTIONS
|
|
|
22 ====================
|
|
|
23
|
|
|
24 I'm impressed that this is working. It took a major restructuring of the
|
|
|
25 internals of gaim. Everything had been based around one connection, and that
|
|
|
26 connection used one protocol or the other. Now, there are many connections, and
|
|
|
27 each connection may be using a different protocol. Most of the functionality is
|
|
|
28 complete but the UI hasn't been updated to reflect all of the different users.
|
|
|
29 This change isn't going to be complete for quite some time so just bear with us
|
|
|
30 as we try to get things operational again.
|
|
|
31
|
|
|
32
|
|
|
33 BUDDY LIST
|
|
|
34 ==========
|
|
|
35
|
|
|
36 The buddy list is completely fucked up. It needs to be heavily modified to be
|
|
|
37 able to support The Change. But logging in as only one user makes it work as
|
|
|
38 it always did.
|
|
|
39
|
|
|
40 This may be changed, but here's how the buddy list cache currently works. When
|
|
|
41 you sign on it imports the list from the name you sign on as. When the list is
|
|
|
42 saved, it is saved to all of the signed on users. This means that when you sign
|
|
|
43 on two or more names at once their lists will be merged.
|
|
|
44
|
|
|
45
|
|
|
46 TOC
|
|
|
47 ===
|
|
|
48
|
|
|
49 TOC is working reasonably well.
|
|
|
50
|
|
|
51
|
|
|
52 Oscar
|
|
|
53 =====
|
|
|
54
|
|
|
55 Oscar is working reasonably well. Please see gaim/libfaim/README.gaim for more
|
|
|
56 details on Oscar.
|
|
|
57
|
|
|
58
|
|
|
59 Applet
|
|
|
60 ======
|
|
|
61
|
|
|
62 I'll be amazed if the applet compiles. If it compiles, I'll be amazed if it
|
|
|
63 doesn't segfault. But technically nothing drastic changed with the applet in
|
|
|
64 The Change, so it may end up working just fine. I don't have the time nor the
|
|
|
65 energy to test it right now though; I'll come back to it as soon as the app is
|
|
|
66 stabilized.
|
|
|
67
|
|
|
68
|
|
|
69 Plugins/Perl
|
|
|
70 ============
|
|
|
71
|
|
|
72 The current plugin/perl system is in complete disarray as things are being
|
|
|
73 totally restructured inside gaim, in hopes of adding a more powerful plugin
|
|
|
74 system (one that can hopefully support Protocol Plugins (see PRPL comments)).
|
|
|
75 While The Change is taking place, most plugins won't compile (and we have set
|
|
|
76 all plugins in gaim/plugins not to compile by default). However, ones that have
|
|
|
77 been previously compiled may or may not work. The only way to know is to load
|
|
|
78 the plugin and test it.
|
