Maybe we should say "RFTM" or in this case "RTFGPL". If is easy to see how non-GPL modules could be linked to GPL code. Two methods come to mind:
(1) If the modual were "general purpose" in the sense that it COULD be used with something other then Asterisk. In other words the modual does not depend on Asterisk and uses a public interface. Codecs could be a perfect example if they were also used in other telephony systems. This would be just like running comercial software under the the Linux OS. (2) It could also be the case that the author of a system like Asterisk specifically allows non-GPL'd modules. This is the case with the Linux kernel and non-GPL'd drivers. Linus specifically allows it. --- Eric Wieling <[EMAIL PROTECTED]> wrote: > On Mon, 2003-09-29 at 09:40, Mark Spencer wrote: > > > > 2) if you build your application as a module that loads into a > stock > > > asterisk server, you do not have to disclose your source > > > > This is FALSE. Even modules for Asterisk MUST be released under > GPL, > > unless you obtain a license to release them outside of GPL from > Digium. > > You mean like codec_g729b.so? > > -- > Sample configs and more: http://www.fnords.org/~eric/asterisk/ > > BTEL Consulting > +1-850-484-4535 x2111 (Pensacola) > +1-504-595-3916 x2111 (New Orleans) > +1-877-677-9643 x2111 (Toll Free) > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users ===== Chris Albertson Home: 310-376-1029 [EMAIL PROTECTED] Cell: 310-990-7550 Office: 310-336-5189 [EMAIL PROTECTED] KG6OMK __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
