2d36152296
Since libpurple doesn't mark individual account settings as "required" or not (Pidgin will accept account settings even with all-blank answers, unlike Cardie), every setting was marked as required by Cardie, just to err on the side of caution. But that's not necessary now, and was bad to begin with (especially for Jabber, etc, with superfluous options)― in the case of libpurple, we can follow Pidgin's example. Cardie will accept account settings with mostly-blank options, but the add-on will send an error (and disable the account) when it doesn't work. |
||
|---|---|---|
| application | ||
| data | ||
| libs | ||
| locales/purple | ||
| protocols | ||
| smileys | ||
| Contributors | ||
| License | ||
| Makefile | ||
| Makefile.common | ||
| README.md | ||
Cardie
A multi-protocol chat program.
Building
You can make Cardie and its protocols with:
$ make
Or one-by-one:
$ make libs; make app; make protocols
Cardie itself requires the expat_devel package, the XMPP protocol requires
gloox_devel, and the libpurple add-on requires libpurple_devel and
glib2_devel.
The (provisional) IRC protocol requires libircclient_devel, openssl_devel,
and zlib_devel, though you have to build it specifically:
$ make -f protocols/irc/Makefile
License
Cardie itself is under the MIT license, but licenses vary for the included libraries and add-ons.
The xmpp and purple add-ons are under the GPLv2+, and irc the MIT license.
libsupport is under the MIT license, though containing some PD code.
librunview contains code from Vision, and is under the MPL.
libinterface is under the MIT license.