Suggested Correction for "Why you should use a BSD style license for your Open Source Project"

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Suggested Correction for "Why you should use a BSD style license for your Open Source Project"

Hamid Sarmadi
Hi,

Here [1], under the section "The origins of Linux and the LGPL", it is written that:

"If you statically link an application with glibc, such as is often required in embedded systems, you cannot keep your application proprietary, that is, the source must be released."

However in these licenses it states that object code can be distributed as an alternative to the source code;

In the LGPL 2.1 we can read:

"... if the work is an executable linked with the Library, [accompany the work] with the complete machine-readable "work that uses the Library", as object code and/or source code ..."

and in LGPL 3.0 we can read:

"... [Convey] the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version ..."

where "Corresponding Application Code" is:

"... the object code and/or source code for the Application ...".

It would be great if someone could correct the mentioned statement in the cited document.

Thanks a lot,
Hamid Sarmadi

[1] https://www.freebsd.org/doc/en_US.ISO8859-1/articles/bsdl-gpl/article.html#origins-lgpl
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "[hidden email]"