I have ported some LGPL code from Java to C#, which I plan to release as an open source component. Do I have to release my new library under LGPL too, or can I go with something less restrictive like MS-PL?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have ported some LGPL code from Java to C#, which I plan to release as an open source component. Do I have to release my new library under LGPL too, or can I go with something less restrictive like MS-PL?
Since you’re basing your work on the original LGPL work, it seems to me that your work is a derivative of the original, and so section 2 of the license applies: Your code needs to be LGPL or, at your option, GPL. (The wording is different in versions 2 and 3, but it’s the same section.) But I’m just a programmer, so what do I know? You’re asking a question about the law, so your best course of action is to ask a lawyer.