Live data from Hacker News

ScummVM on the App Store

apps.apple.com

101–110 of 197 posts

Re: ScummVM on the App Store

#101
Some Free Software projects are simply to good to be true. ScummVM is one of them.

I remember fondly replaying Monkey Island on my Linux machine thanks to it.

Re: ScummVM on the App Store

#103
post #43
post #4

Is there a place where I can legally obtain images to run on the vm?

https://wiki.scummvm.org/index.php?title=Category:Freeware_G... but hm, that category is larger than the category of supported games ... clicking through to the "where to get" link gives a more curated list. There are 4 shipped in most Linux distros (probably more a matter of exact license than quality alone): Flight of the Amazon Queen - everything you'd expect from a fantasy adventure; play this if nothing else Ben…

> probably more a matter of exact license

Yep, they were freewared.

> quality

I have the experience with Flight and Steel Sky only, but they are good.

Re: ScummVM on the App Store

#105

Earlier quoted context omitted.

That would be perfectly legal under the GPL, right? It doesn't say you're not allowed to modify the code, just that you have to distribute the modified code in its entirety. If what Apple is distributing is sufficient to build (their version of) bash, it's perfectly fine.

If the code is what Apple used to build what they're distributing, then yes this is valid. (For this case at least, they have a tendency of doing this a lot and I suspect the change to bash was made just to address this specific complaint while missing every other place they strip out code.)

I tried to rebuild bash a while back on macos and couldn't do it because the source code was not available for rootless.h. I guess someones complaint finally got some action from apple.

I remember doing macos kernel debugging (in the non-gpl code apple distributes) and it was pretty evident that the code they distribute like xnu is NOT the code that is in the OS. Stack traces had lots of functions apple keeps to itself. Looking in the distributed code shows suspicious blank lines where automated tools must remove apple-only source.

Re: ScummVM on the App Store

#106
post #15
post #2

hmmm I suspect this is because it is GPLv2 which doesn't require the freedom to RUN the program (which apple doesn't give you) apple seems to ship software with gplv2 (old bash, etc) but no GPLv3 software. ...even though they are technically in violation of the GPL by modifying and shipping bash binaries without full source - it is missing rootless.h (not the X11 file)

GPLv3’s anti-Tivoization clause specifically targets software bundled with a device, which this is not. There’s plenty of GPLv3 software distributed by its developers on the App Store and nothing in the text of the GPL forbids distribution in a proprietary marketplace.

hmmm. I thought that software loaded on an apple device is DRM'd, meaning it cannot be installed or run without an apple id (basically you must ask apple permission to run the program).

GPLv2 didn't prevent this, but I thought GPLv3 conferred additional rights to the user.

I remember RMS saying, "I realized I had to explicitly say the freedom to RUN the program" I believe about revising GPLv2 to GPLv3

Re: ScummVM on the App Store

#107
post #30

Earlier quoted context omitted.

Is it GPLv3 or AGPL? Their reasons (their excuses? At this point I'm not convinced at all) to ban AGPL are documented at [1]. [1] https://opensource.google/documentation/reference/using/agpl...

What doesn't make sense? They don't want AGPL code to accidentally end up anywhere that's publicly accessible, and a lot of the code in their monolith is used across many different products, so a blanket ban seems entirely reasonable. What motivation do you think they have to lie about this?

Not speaking about code, they ban use of AGPL software. This does not make sense to me.

Software you use does not magically [1] end up in your code base, or you are doing something horribly wrong, I can't even begin to imagine how. Like, "Whoops, I downloaded and executed this AGPL-licensed binary, and now this Google process running on my laptop (or phone!) has automatically fetched its source code and put it to prod and linked it to our software, and now oh no, all our code are belong to GNU!". This is ridiculous. This is some massive, solid bullshit we have here.

You can use AGPL software for any purpose within the law, no strings attached. You never need to touch the code, and if you do, you never need to link your product to it. It does not take a lawyer to understand this simple concept. Proprietary software have more restrictions than that, you'd better not have third party proprietary code ending up in your product, although it's not banned at Google. I hope they do check license compliance on their code base anyway, there are automatic scanners for this. So the chances of some AGPL code ending in their repositories seem vanishingly small.

As for why Google would be dishonest, of course we have no proof and we can't know for sure AFAIK. By default I side with Drew DeVault [2], to me this is anti-AGPL propaganda and their goal is to discourage people from licensing their software under AGPL so they have a bigger pool of open source projects they can potentially reuse without having to contribute back, and it works because now people are afraid to license their stuff under AGPL because "businesses" "often" have an AGPL ban. I know of exactly two companies banning AGPL: Google and Apple. Apple already did that with GPLv3 (AGPLv3 being GPLv3 + a clause). Again, does please the big company (and come on, outdated bash and GNU tools on Mac does not make any kind of sense, the GPL never restricted stuff at the process level interface). I'm sure there are smaller businesses thinking that if Google and Apple ban those licenses, they must be bad and they should do too to be safe, while not having a business model where it even makes sense, playing Google and Apple's game.

If I'm to license software under AGPL, I'm giving Google the right to use this software. That they don't want to use it is their loss. They are doing this to themselves.

[1] https://en.wikipedia.org/wiki/Magical_thinking

[2] https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html

> they want to discourage people from using the AGPL, because they cannot productize such software effectively [...]

> By discouraging the use of AGPL in the broader community, Google hopes to create a larger set of free- and open-source software that they can take for their own needs without any obligations to upstream

Re: ScummVM on the App Store

#108
post #21
post #2

hmmm I suspect this is because it is GPLv2 which doesn't require the freedom to RUN the program (which apple doesn't give you) apple seems to ship software with gplv2 (old bash, etc) but no GPLv3 software. ...even though they are technically in violation of the GPL by modifying and shipping bash binaries without full source - it is missing rootless.h (not the X11 file)

> GPLv2 which doesn't require the freedom to RUN the program It does. This is the first freedom of free software. I'm not sure the issues with distributing GPL software on the App store are specific to the GPLv3. I don't fully understand things on this, but [1] seems to be a good entry point. > apple seems to ship software with gplv2 (old bash, etc) but no GPLv3 software. This is an Apple policy / a choice that they…

> It does. This is the first freedom of free software.

I don't think so:

The Free Software Foundation explicitly forbade tivoization in version 3 of the GNU General Public License.

https://en.wikipedia.org/wiki/Tivoization

I think this is one of the reasons GPLv3 came along.

Re: ScummVM on the App Store

#109

How’d this get past app review? Apple has allowed zero emulators of any type on the App Store. I bet this gets crushed.

“[Apple's codex] is more what you’d call ‘guidelines’ than actual rules.”

I decline to acquiesce to your request.

That means 'no'.

Post reply on HN