Re: [mpg123-devel] LGPL license violation on mobile versions of GTA San Andreas and more

[Thomas B. <to...@tr...>]

On 2023-07-09 10:25, Alfredo Cajá wrote:
> El dom, 9 jul 2023 a la(s) 08:32, Thomas Orgis (tho...@or...)
> escribió:
> 
>> That's annoying because it wouldn't be that hard to comply and still 
>> do
>> business with the closed-source parts. Although: In the case of an
>> Android/iOS app, it not so trivial for a user to replace the mpg123
>> build in it (compared to switching a .dll file in Windows), but it's
>> technically possible.
>> 
Hi, that's an interesting topic, I was trying to understand the exact 
implications of LGPL libraries just recently and came to the conclusion 
that a legal use in non-licensed or incompatibly licensed code is only 
possible with external, e.g. not statically linked LGPL library.
To ship a binary which is using the LGPL library, i understand it so 
that it can happily be shipped along the (e.g. close source) binary, iff 
the license is available and the source code of the exact library 
shipped is also made available. The unclear was if the library can be 
shipped along the binary or if it has to be already on a system or if it 
has to be installed in a separate process.
As a side-note, the "files" app, which is pre-intsalled on iOS, recently 
revealed while fiddling, that it uses libsndfile. Which i found odd, 
since libsndfile is not even LGPL. It would mean that the "files" app is 
GPL'ed?
Good luck Thomas hunting down the violators using the exceptional 
libmpg123.
Greetings
Thomas