Idle thought: can you build Google Chrome's `chrome` binary from Chromium source code, verbatim? Is this documented anywhere? If not, isn't this an LGPL violation, since it embeds Blink which is LGPL-licensed?
-
Show this thread
-
This Tweet is unavailable.
-
Replying to @NedWilliamson
Then it's an LGPL violation. The LGPL requires that the user be able to relink your code with a modified LGPL library.
1 reply 0 retweets 2 likes -
Replying to @marcan42 @NedWilliamson
Unfortunately, I don't think it is a violation, unless they have proprietary bits inside of blink itself. LGPL allows you to use the lib in a proprietary bundle.
1 reply 0 retweets 0 likes -
Replying to @purpleidea @NedWilliamson
Have you read the actual license? LGPLv2.1 requires that the user be able to replace the LGPL'ed bits with their own. Yes, you can link it with proprietary bits, as long as you meet that condition. That means using dynamic linking or distributing .o files for the proprietary bits
1 reply 0 retweets 1 like -
Replying to @marcan42 @NedWilliamson
I have, which section are you referring to? #2 " If identifiable sections of that work are not derived from the Library" #6 "As an exception to the Sections above... ?
1 reply 0 retweets 0 likes -
Replying to @purpleidea @NedWilliamson
Read section #6 again. 6a) "If the work is an executable linked with the Library, with the complete [...] object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library."
2 replies 0 retweets 0 likes
6b) "Use a suitable shared library mechanism for linking with the Library." Google does neither 6a nor 6b, if /opt/google/chrome/chrome contains proprietary bits and cannot be built entirely from Chromium source.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.