On Tue, Aug 12, 2008 at 07:18:10AM +0700, si Nung wrote: > > Linknya bisa diakses di sini : > > http://www.kaskus.us/showthread.php?t=937085 > > > 2. http://lurker.clamav.net/message/20080717.075437.e573caec.en.html > > == > kopas (link #2) sbb : > > Author: Nigel Horne > Date: 2008-07-17 07:54 UTC > To: clamav-win32Subject: Re: [clamav-win32] Question regarding using libclamav > Pandu Poluan wrote: >
Biar nggak salah paham, lengkapnya di sini: http://www.nabble.com/Question-regarding-using-libclamav-td18397216.html Dalam konteks ini, mungkin FAQ berikut relevan: http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLPluginsInNF Can I apply the GPL when writing a plug-in for a non-free program? If the program uses fork and exec to invoke plug-ins, then the plug-ins are separate programs, so the license for the main program makes no requirements for them. So you can use the GPL for a plug-in, and there are no special requirements. If the program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. This means that combination of the GPL-covered plug-in with the non-free main program would violate the GPL. However, you can resolve that legal problem by adding an exception to your plug-in's license, giving permission to link it with the non-free main program. Intinya, kalau liblamav dipanggil dengan fork atau exec, maka itu dianggap program terpisah. Tapi kalau dipanggil lewat fungsi dalam library libclamav, maka itu pelanggaran/dianggap sebagai satu kesatuan program. Kalau dari dokumen libclamav, dipanggilnya lewat fungsi. http://www.clamav.net/doc/latest/html/node39.html Kesimpulan saya pribadi, ini pelanggaran. Memang seharusnya libclamav dilisensikan LGPL, bukan GPL. -- fade2blac -- Berhenti langganan: [EMAIL PROTECTED] Arsip dan info: http://linux.or.id/milis
