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
-
Replying to @marcan42
wouldn't this only be a problem if blink links to the binary part, not the rest of the chrome code. Else opera have an even bigger problem. https://chromium.googlesource.com/chromium/src.git/+/master/LICENSE … is the licence for the whole project.
1 reply 0 retweets 0 likes -
Replying to @ewanm89
The `chrome` binary includes Blink, therefore if that binary cannot be built from Chromium code, it includes proprietary parts and everything is linked together. That file is not the license for the whole project. It's just the top-level license. Blink is licensed differently.
3 replies 0 retweets 1 like -
Replying to @marcan42
What you are suggesting would stop the whole point of LGPL which is so it can be used in proprietary applications as a library and keep the library under it's own licence. Any change to library needs to be open, but not changes to the application using it.
1 reply 0 retweets 0 likes -
Replying to @ewanm89
You're missing the finer points of the LGPL (see my other reply). You do *not* need to open up your proprietary code but you *do* need to have a separable boundary between it and the LGPL code.
1 reply 0 retweets 0 likes
Chrome does *not* have such a separable boundary within its main binary, therefore the conclusion is that the only other way it can comply with the license is by having that binary be 100% open 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.