this post was submitted on 05 Jul 2024
35 points (100.0% liked)
Open Source
29773 readers
225 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Anything that uses *GPLv3 license (which includes the anti-tivoization clause) has to have some way of swapping out those libraries.
Just checked the tivoization definition. (Guess I should have done so, when reading the original thread, when I felt unsure from their explanation of the word).
So, it has to be runnable on the same hardware after modification. It makes sense now.
I seems like something that would be good in case the solution is being used for a long period and would make sure the user doesn't have to bear the burden of finding another platform that would run the binary, in case a library update is required. This would be in the interest of even corporate clients.
CC BY-NC-SA 4.0