Thank you Nokia (YATYNP)

January 14, 2009

Back with the “What does KDE mean to you?” image series, it was important to note the tone of the phrase “KDE is ours.”  It’s unfortunate that humans can be greedy and think the phrase implies exclusivity or ownership.  But nothing can be more inclusive in the tone and the imagery.  And today it gets more inclusive.  The family gets bigger.

As many note, Qt 4.5.0 will be relicensed as LGPL.  Thanks to Qt Software members that orchestrated the initiative, to Nokia and Qt Software at large for taking this leap and to the FreeQt foundation.


The barrier to KDE participation just keeps getting lower.


3 Responses to “Thank you Nokia (YATYNP)”

  1. KDE Fan Says:

    This pictures are so damn cool. Awesome!

  2. erm Says:

    Nothing has changed!

    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.

    When a “work that uses the Library” uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.

    If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)

    Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.

    I did not look at the Qt sourcecode, but usually templates and macros are defined in header files and if you include a header file which contains e.g. a template definitions which is longer then 10 lines of code, you have to release your code under LGPL as stated above. I think that is why people usually use GPL + runtime exception.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: