#GPL software license question. Let's say you are packaging a project and you make changes to the project that are counter to what a developer intends.
Can you still call it the same project name? If you can't - how does the original author convince the packager not to call it the same name ?
ex: project omega is a GPL'd licensed code. Someone comes along, packages it - modifies it because they disagree with code that asks for money effectively removing it. Can they still call it omega?
"Someone comes along, packages it - modifies it because they disagree with code that asks for money"
honest question (and I know that it is not your main point, I am just curious):
Do you know any cases of the example you gave actually happening with a distro package distributed in a distro official repositores?
@sri Do you recall if it was an official package of a repo like debain main repos, or if a community repo like AUR?
@joao I believe it was a community repo AUR. I believe the conversation was with an Arch packager.
@joao I saw this on twitter - where a packager threatened to do that to anyone tries to ask for money within the app. They were adamant that nobody can ask for money. I unfortunately did not save that thread.