I've come across 2 PPAs today which are or have been broken in hopes of making money. In one case, some dependencies have been set as private to break the main packages (like ffmpeg5). This is causing some open source project builds to fail (when these relied on these PPAs) and it makes a bunch of documentation useless.<p>2 examples:<p>- https://launchpad.net/~savoury1 - currently broken packages<p>- https://web.archive.org/web/20191216131452/https://launchpad.net/~jonathonf - packages have been broken in the past - then made available again<p>I'm all-in for donating to package maintainers, but this bait and switch strategy feels a bit evil.<p>Thought on this?
A lot of people/companies have painted themselves into corners where they made everything free for years then later they decided that they needed to make money. But now they can't turn on any business models that actually work because they irrevocably gave away everything. So people are trying to find the least-bad business model and it isn't pretty. These people are not mean; they're just desperate.<p>Having said that, it's rude to break existing packages. Let it stagnate and put the updates in a different package if you want, but don't deliberately break something that used to work.
If the packages are of GPL'ed software, then you (anyone) are within your rights to charge a fee to download the software:<p><a href="https://www.gnu.org/licenses/gpl-faq.en.html#DoesTheGPLAllowDownloadFee" rel="nofollow">https://www.gnu.org/licenses/gpl-faq.en.html#DoesTheGPLAllow...</a><p>Of course, in order to comply with the GPL, you must make the source available as well. Which means, anyone else can turn around and either do the same thing, or even make a copy available for free:<p><a href="https://www.gnu.org/licenses/gpl-faq.en.html#DoesTheGPLRequireAvailabilityToPublic" rel="nofollow">https://www.gnu.org/licenses/gpl-faq.en.html#DoesTheGPLRequi...</a><p>If anyone feels strongly enough about these package maintainers charging a fee, they are welcome to pay the fee and then make the packages available free of charge.<p>But, that would be work. Less work than the work done by the original package creator, but still, work.<p>And, many people want to be compensated for their time. Ultimately, as long as the package maintainer charges a reasonable enough fee that the value provided exceeds the relative cost of the fee, then everyone wins.
I think the moral of the story is: don't rely on PPAs for long term projects - there is a trend to create packages to break them once people integrated them in their scripts/code/infrastructure.<p>Instead, install packages from official reliable sources.