Changeset 04f0c10

Timestamp:

2010-10-03T02:50:20Z (14 years ago)

Author:

Wilmer van der Gaast <wilmer@…>

Branches:

master

Children:

25b5a4a

Parents:

8e9e2b7

Message:

At least for now, only enable OTR if the user specifically asks for it.
Distros can now ship a bitlbee-plugin-otr package (that should work with
both bitlbee and bitlbee-libpurple).

Files:

• configure (modified) (3 diffs)
• doc/README (modified) (1 diff)

configure

@@ -34 +34 @@
 gcov=0
 plugins=1
-otr=auto
+otr=0
 
 events=glib
@@ -73 +73 @@
 
 --purple=0/1    Disable/enable libpurple support        $purple
+                (automatically disables other protocol modules)
 
 --debug=0/1     Disable/enable debugging                $debug
@@ -78 +79 @@
 --gcov=0/1      Disable/enable test coverage reporting  $gcov
 --plugins=0/1   Disable/enable plugins support          $plugins
---otr=0/1       Disable/enable OTR encryption support   $otr
+--otr=0/1/auto/plugin
+                Disable/enable OTR encryption support   $otr
 
 --events=...    Event handler (glib, libevent)          $events

doc/README

@@ -67 +67 @@
 platform. Any recent version of GLib (2.4 or higher) will work.
 
-Off-the-Record encryption support will be included by default if the
-configure script finds libotr in one of the usual places. You can pass
---otr=1 or --otr=0 to force it on or off, respectively.
+Off-the-Record encryption support can be included if libotr is available on
+your machine. Pass --otr=1 to configure to build it into BitlBee, or
+--otr=plugin to build it as a separate loadable plugin (mostly meant for
+distro packages).
 
 These days, many IM protocols use SSL/TLS connections (for authentication