Hi Tom, Have a read through the FAQ at http://www.fsf.org/licensing/licenses/gpl-faq.html and perhaps get in touch with someone knowledgeable about the GPL (lawyer types, or someone at the FSF) to help clarify.
In particular, http://www.fsf.org/licensing/licenses/gpl-faq.html#IfInterpreterIsGPL - which indicates that an program written to be interpreted by a GPL-covered interpreter (which OpenBD may or may not be categorised as) are not required to be covered by a GPL type licence. Of course, it then goes on to talk about if the interpreter provides 'bindings' to other facilities, and these facilities are GPLd, then your program also needs to be GPLd. It might be worth looking at other GPLv3-covered applications that are similar in context to OpenBD, and see how their use has been categorised - if it can be seen as purely an interpreter then it would appear that you can do as you originally planned (I'm guessing you would still need to provide notices to show that the OpenBD component is GPLv3, but your application code can be licensed under your own terms) Cheers Dave On Thu, Mar 19, 2009 at 3:59 AM, tom thomas <[email protected]> wrote: > Ok, using cf was the easy route to go. I guess I will have to rewrite my > program into vb.net. > > Thanks, > Tom Thomas > > At 12:51 PM 3/18/2009, you wrote: > > Its GPLv3 -- so anything that is released, that has OpenBD bundled has > to be also GPL. > > Share the love! :) > > > Alternatively you can let them download OpenBD independently and install > it themselves. > > > > tom thomas wrote: >> OpenBD >> >> At 12:37 PM 3/18/2009, you wrote: >> >>> Licensing what though? >>> >>> OpenBD? >>> NewAtlanta's BD.NET? > > > > > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
