flathub / edu.mit.scratch

Flathub

Flathub is the central place for building and hosting Flatpak builds.

Using the Flathub repository

To install applications that are hosted on Flathub, use the following:

flatpak remote-add flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install flathub org.gnome.Recipes

To install applications from the beta branch, use the following:

flatpak remote-add flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo
flatpak install flathub-beta org.godotengine.Godot

For more information and more applications see https://flathub.org

Contributing to Flathub

For information on creating packages or reporting issues please see the contributing page.

Note: this repository is not for reporting issues related to the flathub.org website itself or contributing to its development. For that, go to https://github.com/flathub-infra/website

edu.mit.scratch's Issues

Update runtime to 19.08

Please update Scratch to 3.21

Scratch 1.18 has bug with text-to-speech block. The fix in 3.21

https://scratch.mit.edu/discuss/topic/450602/?page=3

Bundles libffmpeg.so containing patent-encumbered codecs

$ strings /app/scratch/libffmpeg.so | grep ff_h264 | wc -l
133
$ strings /app/scratch/libffmpeg.so | grep ff_aac | wc -l
36

https://www.npmjs.com/package/electron-packager-plugin-non-proprietary-codecs-ffmpeg appears to exist. Internally, it just grabs an ffmpeg binary from https://github.com/electron/electron/releases/tag/v6.1.7 and these appear not to have patent-encumbered codecs, though I can find no information about how they are compiled which does not exactly inspire confidence.

Would like Scratch3 for i386

I run Debian Buster with Raspberry Pi Desktop on an Eee PC 1001HA netbook with Atom N270 x86-32 only and it would need support for architecture i386 in order to run (i386 is actually compiled as i686 AFAIK).

Content attributes don't make sense

I'm wondering why scratch is reporting that it's content is violent or uses illicit substances etc.

Installed on elementary os via appcenter which populates it's information directly from the appdata.xml as far as I understand.

No ARM support

This Flatpak is currently built only for x86_64. Endless is interested in two flavours of ARM:

• We have production armhf (32-bit) devices. Our old in-house Flatpak of a much older version of Scratch was built for armhf.
• We hope to start shipping arm64 images soon.

In IRC discussion about the x86_64-only limitation, @refi64 explained

it's because the build steps use chromedriver which only has official binaries for x64, if there's need for it I can e.g. pull Fedora's binaries for other architectures but at the moment it didn't seem critical