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
-
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.
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.
-
-
I never said Blink wasn't licensed differently, but if chrome's use of blink is no different that chromiums then blink in the code does not link to anything proprietary in chrome. And they can point to chromium as a full opensource implementation where all changes exist...
-
That's not how the LGPL works. The LGPL requires that I be able to modify Blink, then link it back into proprietary Chrome and be able to use it. Hence the requirement to either use dynamic linking or distribute relinkable object files.
- Show replies
New conversation -
-
-
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.
-
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.
- Show replies
New conversation -
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.