Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

"The LGPL is inappropriate for statically linked [closed source] software" – that seems to be inaccurate, as in fact LGPL and static linking is legally possible (see).

tanius
– tanius

2020-05-31 02:35:57 +00:00
Commented May 31, 2020 at 2:35
Your position appears correct. See gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic But it's extra work and extra things to ship. Can you get away with it? Yes. Do you want to spend the effort? Possibly not.

Adam Hawes
– Adam Hawes

2020-06-12 03:59:44 +00:00
Commented Jun 12, 2020 at 3:59

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »