My team lead is making us use open source libraries licensed under LGPL 3.0 for our embedded electronics project. The way our software is designed will not follow the LGPL 3.0 rules - the user cannot relink the library and recompile it themselves.
Can I get fucked or does it realistically not matter if we're misusing open source code in our relatively niche product from a small turd world company?

>>106147774 (OP)
fsf and gnu project keep lists of all past precedence in courts across the globe. If the software is small scale and no one notices nothing will happen. But if it becomes big...
https://en.wikipedia.org/wiki/Open_source_license_litigation

>>106147817
Would anyone even know we used that licensed code, if it's the firmware of a device that the end user isn't supposed to care about, once it's been installed in their building?
It's a library that enables a certain software function on a certain piece of hardware, but the end user isn't ever meant to look at the device on the inside.

>>106147774 (OP)
Literally no one cares if you steal code. There is one exception; if you're at a big company they might have rules against doing so because people that catch stolen source code because people might sue them for a payout.

>>106147914
My company doesn't care. My team lead said don't worry about it. Am I really overthinking it?

No one cares. Just steal shit.

>>106147774 (OP)
most common break in GPL is Sony devices.
Playstations, all Sony-Ericsson and newer phones.
Apple was running huge 'macos based on FreeBSD lie'
https://www.reddit.com/r/unix/comments/8hwlcg/ive_heard_that_ios_and_macos_is_based_off_freebsd/

>>106147888
It would be extremely painful.

just don't use VCS

>>106147774 (OP)
Do what he says, just get it in writing so you can shift the blame to him in case your company gets sued

>>106147774 (OP)
just "scale" the rules

>>106150466
This. Make sure to take notes on the criminal conspiracy to cover your own ass.

>>106147933
Let the FSF and the library owner(s) know.