Hi,

The LGPL (http://www.gnu.org/copyleft/lesser.html) document is, at
best, confusing, hard to understand, and purposely obfuscated. It
doesn't provide a clear description of what's allowed and not allowed,
the specific requirements, or clear definitions of 'work that uses the
Library' and 'derivative of the Library' (2nd paragraph of section 5
of LGPL). Seems no one can afford a lawyer to decipher the text, and
the lack of any clear explanation/FAQ on the internet suggests the
license text is too generic to answer any of the specific FAQs that come up in
discussions.

So, I would like a clear, authoritative answer, and not simply
someone's "interpretation" of the license text, for the following
specific context:

Given the following...

1. I am developing an application using PySide+Python for commercial usage.

2. The application will be distributed using various package building schemes 
available on platforms in such
   a way that it's self-contained. This means I would be including .dll/.so and 
other files along with my
   package.

3. I may compile PySide from sources only because binary package is not 
available for X platform. (For example
   various Linux distros)

4. Am I allowed to compile PySide statically just to reduce size and number of 
dependencies?

5. I won't be including any source code in any format along with the package.

6. I'll use my own license along with my application.

7. Do I have to copy PySide's LGPL license along with the application?

8. Do I have to give credit to PySide inside my application? (For example 
Help>About)

9. Any other implications?

10. Am I Missing anything else?

Best Regards

Prashant


_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside

Reply via email to