view README.CVS @ 8383:ae15e717ca75

[gaim-migrate @ 9111] (00:18:52) lschiere: marv: https://sourceforge.net/tracker/?func=detail&atid=300235&aid=908071&group_id=235 (00:21:24) marv: what does gc->wants_to_die = TRUE; do? is that some sort of hint for the autoreconnect plugin? (00:21:43) lschiere: kinda sorta (00:21:51) lschiere: if a gc wants to die, you signed off (00:22:01) lschiere: if it doesn't, then something killed it, and it should be reconnected (00:22:41) lschiere: i'm not sure how we used to handle that kind of thing for aim (00:23:03) lschiere: but basically if that's what he's doing, he's mimicing you signing off manually (00:23:52) marv: yeah, all the patch does is add that line right before the gaim_connection_error when yahoo receives a patch telling us we got signed off because we signed on with another client (00:24:22) lschiere: i dare say it would work, as long as we can uniquely id when we are kicked off for that reason (00:25:07) marv: i think we do a pretty good job of that, i haven't heard any reports of anyone getting that message when that's not what happened. (00:25:22) marv: then again, i don't remember when i added that, and if yahoo's worked since then. (00:25:36) lschiere: *nods* basically, Rob Foehl figured out a predictable way to work around yahoo being too dumb to handle 2 instances of the same sn on at once. Jabber's done that for years, and aim even figured it out, so you'd think yahoo would get a clue... ;-) committer: Tailor Script <[e-mail]>

If you plan to use gaim CVS, PLEASE read this message in its entirety!

Gaim is a fast-moving project with a somewhat regular release schedule.  
Due to the rate of gaim development, CVS undergoes frequent bursts of 
massive changes, often leaving behind brokenness and partial 
functionality while the responsible developers rewrite some portion of 
code or seek to add new features.

What this all boils down to is that CVS _WILL_ sometimes be broken.
Because of this, we ask that users who are not interested in
personally tracking down bugs and fixing them (without a lot of
assistance from the developers!) avoid CVS and use releases.  Since
releases will be made often, this should not prevent anyone from using
the newest, shiniest features -- but it will prevent users from having
to deal with ugly development bugs that we already know about but
haven't gotten around to fixing.

If you are interested in hacking on gaim, please read README and
HACKING, and take note of the issues in PROGRAMMING_NOTES.  (Note that
they may be somewhat out of date at times.) Win32 developers, please
read README.mingw.

By far the best documentation, however, is the documented code.  Not
all parts of gaim have yet been documented, but the major subsystems
are falling fast.  If you have doxygen, you can use the Doxyfile in
the toplevel directory to generate pretty documentation.  Otherwise
(or even if you do!), the header files for each subsystem contain
documentation for the functions they contain.  For instance,
conversation.h contains documentation for the entire
gaim_conversation_* API, and account.h contains documentation for the
gaim_account_* API.

If you have questions, please feel free to contact the gaim developers
by email at [e-mail], on IRC at
irc.freenode.net in #gaim, or via the sourceforge forums at
http://www.sourceforge.net/projects/gaim.  Please do as much homework
as you can before contacting us; the more you know about your
question, the faster and more effectively we can help you!

Send patches to [e-mail] or post them in the
Sourceforge forums at http://www.sourceforge.net/projects/gaim.