Re^4: Protecting our work

Here's an interesting interpretation from Sleepycat (BerkeleyDB). While it might not be 100% aplicable to Mysql's license, the definition of the term application would be key here.

Do I have to pay for a Berkeley DB license to use it in my Perl or Python scripts?

No, you may use the Berkeley DB open source license at no cost. The Berkeley DB open source license requires that software that uses Berkeley DB be freely redistributable. In the case of Perl or Python, that software is Perl or Python, and not your scripts. Any scripts you write are your property, including scripts that make use of Berkeley DB. None of the Perl, Python or Berkeley DB licenses place any restrictions on what you may do with them.

Comment on Re^4: Protecting our work

Replies are listed 'Best First'.
Re^5: Protecting our work by salva (Canon) on Aug 29, 2005 at 13:52 UTC
On the GPL FAQ: If a programming language interpreter is released under the GPL, does that mean programs written to be interpreted by it must be under GPL-compatible licenses?.	[reply]
Re^6: Protecting our work by deliria (Chaplain) on Aug 29, 2005 at 18:42 UTC
Quoted from the link in the above post: Another similar and very common case is to provide libraries with the interpreter which are themselves interpreted. For instance, Perl comes with many Perl modules, and a Java implementation comes with many Java classes. These libraries and the programs that call them are always dynamically linked together. A consequence is that if you choose to use GPL'd Perl modules or Java classes in your program, you must release the program in a GPL-compatible way, regardless of the license used in the Perl or Java interpreter that the combined Perl or Java program will run on. DBI and Class::DBI are both released under GPL or the Artistic License. In which case the application to be interpreted by perl is not by definition required to be GPL. Additionally, unless the aplication uses specific Mysql only features, the use of DBI or Class::DBI in the aplication does not limited it to mysql only, which would invalidate this discussion wether or not one is required to release the written perl scripts under GPL.	[reply]