Subject RE: [Firebird-Java] Change firebirdsql license to lgpl only? and,lets release next version.
Author Rodolfo M. Raya

The license considers 2 situations:

1) You compile and link your code and produce a standalone executable that uses the library as a separate file.

2) You compile your code and link it with the library object code and get only one executable file.

Let's suppose we are in Windows world. In case 1) you have a .EXE file plus a .DLL file and in 2) you only have a .EXE file

LGPL license requires the final to user be able to modify the library, recompile it and replace the version you suply. In case 1) the user recompiles the library and replaces the .DLL file only, so your .EXE file can have any license (it can be a commercial application without source code). In case 2) the user needs the object files of your code, therefore your program should be released under LGPL.

Going to Java world: if you distribute your code in one .jar file and firebirdsql.jar as a separate file, your code can have any license you like. If you include some .class files from org.firebirdsql.* in your own application's  .jar file, then you have to distribute your work under LGPL.

To keep things simple: in a commercial environment you should distribute firebirdsql.jar (or any other library you didn't write) as a separate file that your users can replace by themselves.



On Fri, 2002-08-23 at 10:54, Ken Richard wrote:
I am a little confused about the language of distributing a "work that
uses the library".  The following paragraph seems to imply that any code
that links the library must be considered a derivative because it
contains portions of the library.

Does anyone have a clarification?  I read it several times and I cannot
see how I can link my program with LGPL without turning my code into
LGPL.  Am I OK because this is JAVA and there is no "executable"?

5. A program that contains no derivative of any portion of the Library,
but is designed to work with the Library by being compiled or linked
with it, is called a "work that uses the Library". Such a work, in
isolation, is not a derivative work of the Library, and therefore falls
outside the scope of this License. 

However, linking a "work that uses the Library" with the Library creates
an executable that is a derivative of the Library (because it contains
portions of the Library), rather than a "work that uses the library".
The executable is therefore covered by this License. Section 6 states
terms for distribution of such executables.


------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now

To unsubscribe from this group, send an email to:


Your use of Yahoo! Groups is subject to 

 IBM Business Partner
 Microsoft MSDN Business Connection Partner