2004-07-20 08:15:47 +02:00
|
|
|
Since we not support separate network entries, the old supybot.server
|
|
|
|
configuration variable won't work. To fix this, add these lines to
|
|
|
|
your configuration:
|
|
|
|
|
|
|
|
supybot.networks.default: <network>
|
|
|
|
supybot.networks.<network>.server <server>
|
|
|
|
supybot.networks.<network>.password <password>
|
|
|
|
|
|
|
|
Where <network> is the name of the network you're connecting to,
|
|
|
|
<server> is the old supybot.server, and <password> is the old
|
|
|
|
supybot.password.
|
|
|
|
|
2004-07-20 07:42:55 +02:00
|
|
|
Since we support multiple networks and multiple servers now, the
|
|
|
|
--server option has been removed from scripts/supybot, as has the
|
|
|
|
--password option.
|
|
|
|
|
2004-05-07 13:30:42 +02:00
|
|
|
supybot.defaultCapabilities is space-separated now, not
|
|
|
|
comma-separated. You you should remove the commas from this value in
|
|
|
|
your configuration file before loading the bot.
|
|
|
|
|
2004-04-16 10:16:37 +02:00
|
|
|
Version 0.77.2
|
|
|
|
|
2004-04-17 19:17:45 +02:00
|
|
|
This is a drop-in replacement for 0.77.1, with two exceptions. The
|
2004-04-16 10:16:37 +02:00
|
|
|
configuration variable formerly known as
|
|
|
|
"supybot.plugins.Services.password" is now known as
|
|
|
|
"supybot.plugins.Services.NickServ.password", due to the fact that
|
|
|
|
there might be different passwords for NickServ and ChanServ (and
|
|
|
|
ChanServ passwords are per-channel, whereas NickServ passwords are
|
|
|
|
global). If you're using the Services plugin, you'll need to make
|
2004-04-17 19:17:45 +02:00
|
|
|
this change in order to continue identifying with services. The
|
|
|
|
configuration variable formerly known as
|
|
|
|
"supybot.plugins.Babelfish.disabledLanguages" is now known as
|
|
|
|
"supybot.plugins.Babelfish.languages". The configuration variable now
|
|
|
|
accepts the languages that *will* be translated as opposed to ones
|
|
|
|
that are *not* translated.
|
2004-04-16 10:16:37 +02:00
|
|
|
|
2004-04-18 06:10:39 +02:00
|
|
|
Tests and the developer sandbox are not longer delivered with our
|
|
|
|
release tarballs. If you're a developer and you want these, you
|
|
|
|
should either check out CVS or download one of our weekly CVS
|
|
|
|
snapshots, available at http://supybot.sourceforge.net/snapshots/ .
|
|
|
|
|
2004-04-09 19:13:49 +02:00
|
|
|
Version 0.77.1
|
|
|
|
|
|
|
|
This is a drop-in replacement for 0.77.0 -- no incompatibilities, to
|
|
|
|
out knowledge. Simply install over your old installation and restart
|
|
|
|
your bot :)
|
|
|
|
|
2004-01-26 04:51:02 +01:00
|
|
|
Version 0.77.0
|
|
|
|
|
2004-02-11 08:17:11 +01:00
|
|
|
Setup.py will automatically remove your old installations for you, no
|
|
|
|
need to worry about that yourself.
|
2004-02-06 07:41:20 +01:00
|
|
|
|
2004-01-26 04:51:02 +01:00
|
|
|
Configuration has been *entirely* redone. Read the new
|
|
|
|
GETTING_STARTED document to see how to work with configuration
|
|
|
|
variables now. Your old botscripts from earlier versions *will not*
|
|
|
|
work with the new configuration method. We'd appreciate it if you'd
|
|
|
|
rerun the wizard in order for us to find any bugs that remain in it
|
2004-02-17 04:36:50 +01:00
|
|
|
before we officially declare ourselves Beta. Note also that because
|
|
|
|
of the new configuration method, the interface for plugins' configure
|
|
|
|
function has changed: there are no longer any onStart or afterConnect
|
|
|
|
arguments, so all configuration should be performed via the registry.
|
2004-01-26 04:51:02 +01:00
|
|
|
|
2004-01-31 21:51:31 +01:00
|
|
|
Channel capabilities have been changed; rather than being
|
2004-02-01 00:32:47 +01:00
|
|
|
#channel.capability, they're now #channel,capability. It's a bit
|
2004-01-31 21:51:31 +01:00
|
|
|
uglier, we know, but dots can be valid in channel names, and we
|
|
|
|
needed the dot for handling plugin.command capabilities.
|
2004-02-04 08:57:39 +01:00
|
|
|
tools/ircdbConvert.py should update this for you.
|
|
|
|
|
|
|
|
The on-disk format of the user/channel databases has changed to be far
|
|
|
|
more readable. A conversion utility is included, as mentioned before:
|
2004-02-06 07:41:20 +01:00
|
|
|
tools/ircdbConvert.py. Run this with no arguments to see the
|
|
|
|
directions for using it.
|
2004-01-31 21:51:31 +01:00
|
|
|
|
|
|
|
Uh, we were just kidding about the upgrade script in 0.76.0 :) It'll
|
2004-02-04 08:57:39 +01:00
|
|
|
be a little while longer. We do have several little upgrade scripts,
|
|
|
|
though.
|
2004-01-31 21:51:31 +01:00
|
|
|
|
2003-12-12 19:57:54 +01:00
|
|
|
Version 0.76.1
|
|
|
|
|
|
|
|
Almost entirely bugfixes, just some minor (and some less minor) bugs
|
|
|
|
that need to get in before we really start hacking on the next
|
|
|
|
version. Should be *entirely* compatible with 0.76.0.
|
|
|
|
|
2003-12-09 02:36:37 +01:00
|
|
|
Version 0.76.0
|
|
|
|
|
|
|
|
Major bugfix release. A great number of bugs fixed. This is the last
|
2003-12-09 03:36:54 +01:00
|
|
|
release without an upgrade script.
|
|
|
|
|
|
|
|
The only hiccup in the upgrade from 0.75.0 should be that you'll need
|
|
|
|
to update your botscript to reflect the removal of the debug module.
|
|
|
|
We'd rather you use supybot-wizard to generate a new botscript, of
|
|
|
|
course, but if you insist on modifying your existing botscript, take a
|
|
|
|
look at
|
|
|
|
<http://cvs.sourceforge.net/viewcvs.py/supybot/supybot/src/template.py?r1=1.20&r2=1.21>
|
|
|
|
to see what you need to do.
|
2003-12-09 02:36:37 +01:00
|
|
|
|
|
|
|
|
2003-11-22 05:57:17 +01:00
|
|
|
Version 0.75.0
|
|
|
|
|
|
|
|
Don't forget to reinstall (i.e., run "python setup.py install" as
|
2003-11-22 06:00:49 +01:00
|
|
|
root). Sometimes it even does good to remove the old installation;
|
|
|
|
$PYTHON/site-packages/supybot can be removed with no problems
|
|
|
|
whatsoever.
|
2003-11-22 05:57:17 +01:00
|
|
|
|
|
|
|
You will need to re-run supybot-wizard and generate a new botscript.
|
|
|
|
|
|
|
|
The Infobot plugin has been removed from this release; it's not ready
|
|
|
|
for prime time. If you're interested in getting it running (i.e., you
|
|
|
|
want full Infobot compatibility and aren't satisfied with either
|
|
|
|
MoobotFactoids or Factoids) then swing over to #supybot and we can
|
|
|
|
discuss the tests. We simply don't know enough about Infobot to make
|
|
|
|
sure our Infobot plugin is an exact replica, and need someone's help
|
|
|
|
with making the changes necessary for that.
|