How do you even manage to break LGPL lmao all it asks for is attribution, which is like a few line changes on your LICENSE file.
this post was submitted on 27 Dec 2025
164 points (98.2% liked)
Technology
78627 readers
3368 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
Relevant bit
The DMCA filing states that several files in the Rockchip MPP repository are derived from FFmpeg’s libavcodec sources. It lists AV1, H.265, and VP9 decoder files, and claims the copied code is clear because of matching structure, comments, and commented-out calls to FFmpeg functions with their original names.
Much of FFmpeg, including libavcodec, uses the GNU Lesser General Public License version 2.1. This license allows reuse, but only if certain rules are followed. These rules include keeping copyright notices, giving proper credit, and ensuring any shared code remains under an LGPL-compatible license.
The DMCA notice says Rockchip broke these rules by removing the original copyright and author details, claiming the copied code as their own, and sharing it under the Apache license, which does not meet LGPL requirements here.
Sounds like something they should easily be able to comply with. If the relevant ticket in their internal issue tracker is given priority. 😅
Maybe. They cut and pasted the other guys stuff who knows what other stuff is there
They're Chinese, they ain't bothering to read and change the License (especially if they don't have many english-speaking devs)
Cut and paste source code into your repo, which you can do, then offer the whole thing under apache which you cannot do.
I didn't look into how the code is used, but LGPL can still easily get an entire project.
Most people are unaware that even open source projects have licenses: Permissive license, Strong Copyleft, Weak Copyleft etc.
Some resources:
And all those licenses rely on copyright and IP law.
And all those global faceless multicorps requiring you to agree to their 200 page eula rely on that foss licensed goodness, without ever contributing an iota back to the source.
I just wish each video decoder manufacturer didn't feel the need to create their own API that isn't supported by anything.
It feels counter productive when everyone relies on ffmpeg and there are no proprietary secrets left to protect. Just agree on an open standard that saves time and effort for all companies using it while getting tons of goodwill and positive cosmic vibes and maybe even revenue.