This had completely slipped my mind. Sorry for the noise, I received the bug report and forwarded it to you without giving it the proper attention. I should have remembered this before.
Anyway, no harm no foul. Another very small thing that crossed my mind: when compiled with a diferent Gaim version, I get a warning about possible problems arising. That doesn't make much sense to me since gaim's API is supposed to be frosen in the 1.0 tree. Is this some sort of check that someone forgot to remove? Is it triggered by Gaim-enc or Gaim itself? Cheers On Qua, 2005-03-23 at 15:56 -0500, Bill Tompkins wrote: > Cool! I'm very glad to hear that it is in. > > Bug reports are always appreciated. I like to try to keep all outstanding > bug > reports on the SourceForge site, so they don't fall through the cracks. Feel > free to get in touch with me, on either email or IM, if you have questions > about the suitability of taking a bug report upstream by filing it there. > > Gaim-Encryption hasn't used OpenSSL since July, 2003. It uses the Mozilla > NSS > libraries, which are GPL. Arguably, a license exception from me would not be > enough, as the plugin is linked with Gaim: this was one of the driving > factors that prompted me to switch crypto libraries. > > I'm not sure why there is still the perception out there that Gaim-Encryption > uses OpenSSL... > > -Bill -- Leo Antunes <[EMAIL PROTECTED]> | <[EMAIL PROTECTED]> | <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
