Changeset dd34575 for debian/README.Debian
- Timestamp:
- 2008-04-02T13:28:23Z (16 years ago)
- Branches:
- master
- Children:
- 6ff51ff, 85d7b85
- Parents:
- 0db75ad (diff), fa75134 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
debian/README.Debian
r0db75ad rdd34575 1 *** NEWS (Version 1. 1and later) ***1 *** NEWS (Version 1.2 and later) *** 2 2 3 Starting from version 1. 1, BitlBee has a forking daemon mode. The Debian3 Starting from version 1.2, BitlBee has a forking daemon mode. The Debian 4 4 package now uses this mode by default, instead of inetd mode. If you don't 5 5 want to use this, you can disable the init scripts (best way to do this is … … 7 7 should be necessary only once, it won't be touched during upgrades. 8 8 9 -------------------------------------------------------------------------- 9 Another important change in BitlBee 1.2 is the file format used for your 10 personal settings. Everything's now saved in a single .xml (per account, 11 of course) file instead of $nick.accounts and $nick.nicks. One advantage 12 of this new format is that the passwords are actually encrypted instead of 13 just vaguely obfuscated. BitlBee can still read the old files, and will 14 save things in the new format when you save/disconnect. After that, you 15 can safely remove the old-style files (this is recommended). 16 17 I tried making this transition (the new file format but especially, in this 18 case, the inetd->forkdaemon mode change) as smooth as possible, but I'm 19 aware that many BitlBee users will have their own hacks already to run the 20 program. I hope the package won't break any of this for anyone. 1.2-2 21 should fix at least some of the issues. 22 23 --------------------------------------------------------------------------- 10 24 11 25 Debconf should have asked you on what port you want BitlBee to run. If it
Note: See TracChangeset
for help on using the changeset viewer.