-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 12 May 2003 05:54 pm, Zed Pobre wrote: > Unfortunately, yes. Header code is included, and this is legally > sufficent to consider the result a derived work of both the Licq code > and the SSL code.
Well, my reply to this can be one of the following two items: 1. Licq only has an "#include <file.h>" So Licq does not use file.h, the compiler does! The resulting binary doesn't have any code from file.h in it, so the Licq binary is free from that file (as long as function definitions are not made in it, if so see #2). Also, file.h can be the header file of anything and doesn't matter if it is SSL or not. 2. I can make everything extern, so all functions/structures names could be from any library that decides to name them the same as the SSL library. I think #2 is stronger. Jon ______________________________________________________________ Jon Keating ICQ #16325723 [EMAIL PROTECTED] GPG ID: 0x2290A71F emostar on irc.freenode.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+wFKEld1KayKQpx8RAp1UAKDM3FqtnqomHnwC7Xk67wWeFGg7vQCeOsFQ HlU+oP8XCj0L5JIPq59Hizo= =rT9/ -----END PGP SIGNATURE----- ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
