blobjim [he/him]

rustc_codegen_gcc looks pretty cool!

Is Rust support in GCC ready yet? It’s worrying that Linux is now becoming dependent on the massive LLVM project and the Rust reference implementation (also presumably complex?).

There’s a list right on the website: https://plasma-bigscreen.org/get/

Since Plasma bigscreen is part of KDE, you probably want to start with a KDE desktop environment. So just get Fedora Kinoite (performs “atomic updates” which are a little faster and more reliable) or Fedora KDE Plasma Desktop (traditional packages which maybe have a higher chance to break, a little more annoying to update I think).

To install plasma-bigscreen on Kinoite, you run rpm-ostree install plasma-bigscreen and then reboot the computer.

The main Chrome flatpak currently just installs the official RPM file for Chrome. You’re right that the Chromium and Ungoogled Chromium ones do seem to build from source a bit more. I imagine it will just mean a better build process with less patching.

But you can see exactly what it means right in the ticket:

• Create chrome/installer/linux/flatpak/ with packaging scripts and templates for metadata, AppStream metainfo, and launcher entrypoint.
• Add enable_flatpak GN build argument (default false).
• Add package_format to InstallerConfig and omit host desktop integration artifacts (system desktop files, /usr/bin symlinks, AppStream appdata, GNOME default apps, manpages, and AppArmor profiles) when packaging for Flatpak.
• Update common/installer.py with Flatpak configuration and App ID mapping for Chromium (org.chromium.Chromium*) and Google Chrome (com.google.Chrome*).
• Generalize common/desktop.template to support both Flatpak and system-wide desktop execution commands.
• Disable setuid sandbox and zlib compression for non-official builds.
• Update BUILD.gn with flatpak packaging targets and aliases.