3 ms·

> The Rewind Helper contains a statically linked FFmpeg. Wait a minute, that means source code must be provided for the entire binary right? FFmpeg is LGPL, b

> The Rewind Helper contains a statically linked FFmpeg. Wait a minute, that means source code must be provided for the entire binary right? FFmpeg is LGPL, but that only saves you from opening up your whole application if you dynamically link to it. If the helper binary has a statically-linked ffmpeg, that means LGPL applies for the non-ffmpeg code too. Anyone care to make a source code request?

Dylan16807 4y ago
That depends on how hard it is to replace the library despite it being statically linked. But if they are violating LGPL, that doesn't mean LGPL applies to their code. It just means they're violating LGPL.
- EMIRELADERO 4y ago
  They would be violating LGPL if they didn't provide the code upon request. > That depends on how hard it is to replace the library despite it being statically linked. The requirements for providing a way to replace the library are for dynamic linking. Static linking means your program is now fully LGPL, not just the library you linked with.
  - Dylan16807 4y ago
    > They would be violating LGPL if they didn't provide the code upon request. In an indirect way. There is an important difference between "they are obligated to make their code LGPL" and "their code is not LGPL, so they seem to be in violation, but they could make their code LGPL to avoid a violation". > Static linking means your program is now fully LGPL, not just the library you linked with. No it doesn't. Making the program fully LGPL is just an option they have. You can't force them to choose that option, and it does not happen automatically. > The requirements for providing a way to replace the library are for dynamic linking. Static linking means your program is now fully LGPL, not just the library you linked with. Dynamic linking is just one way to do it. Even gnu.org says you can accomplish it with static linking! https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynami... And "must also provide" likely includes "upon request".

Dylan16807 4y ago

That depends on how hard it is to replace the library despite it being statically linked. But if they are violating LGPL, that doesn't mean LGPL applies to their code. It just means they're violating LGPL.

EMIRELADERO 4y ago
They would be violating LGPL if they didn't provide the code upon request. > That depends on how hard it is to replace the library despite it being statically linked. The requirements for providing a way to replace the library are for dynamic linking. Static linking means your program is now fully LGPL, not just the library you linked with.
- Dylan16807 4y ago
  > They would be violating LGPL if they didn't provide the code upon request. In an indirect way. There is an important difference between "they are obligated to make their code LGPL" and "their code is not LGPL, so they seem to be in violation, but they could make their code LGPL to avoid a violation". > Static linking means your program is now fully LGPL, not just the library you linked with. No it doesn't. Making the program fully LGPL is just an option they have. You can't force them to choose that option, and it does not happen automatically. > The requirements for providing a way to replace the library are for dynamic linking. Static linking means your program is now fully LGPL, not just the library you linked with. Dynamic linking is just one way to do it. Even gnu.org says you can accomplish it with static linking! https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynami... And "must also provide" likely includes "upon request".