Language Selection

English French German Italian Portuguese Spanish

Flatpak 1.3

Filed under
Red Hat
  • Flatpak 1.3 Brings Support For Multiple NVIDIA GPUs, Sandboxed DConf

    The Flatpak 1.3 unstable series has kicked off starting the latest round of feature work to this leading Linux sandboxing / app distribution technology.

    Flatpak 1.3.0 is available for testing as the first unstable/development release for what will eventually become Flatpak 1.4. The Flatpak 1.3 release now supports multiple NVIDIA GPUs, support for systems where /var/run is a symlink (e.g. Gentoo), initial support for sandboxed DConf support, and generating the AppStream branch is now much faster on large repositories, among other improvements. There's also the usual assortment of bug fixing and some translation updates in this release.

  • Flatpak 1.3 Arrives with Support for Linux Systems with Multiple Nvidia Devices

    Flatpak developer and maintainer Alexander Larsson released a new unstable release of the Linux application sandboxing and distribution framework, targeting the upcoming Flatpak 1.4 stable series.

    Flatpak 1.3 is here as the first milestone is a series of unstable releases towards the next major and stable new version of the Linux application sandboxing and distribution framework, Flatpak 1.4, adding several new features and improvements like support for systems with multiple Nvidia devices.

    Furthermore, the Flatpak 1.3 release adds initial support for sandboxed dconf, introduces two new options to the build-update-repo command, namely --no-update-[summary,appstream] and --static-delta-ignore-ref=PATTERN, and improves support for large repositories by making regeneration the appstream branch faster.

More in Tux Machines

Android Leftovers

today's howtos

OpenJDK 8 and 11: Still in safe hands

In 2018, Oracle announced that it would only provide free public updates and auto-updates of Java SE 8 for commercial users until the end of January 2019. Java 8 is a very important platform, used by millions of programmers, so this was a big deal. The Java community needed to fill the gap. In February of this year, I was appointed as the new Lead of the OpenJDK 8 Update Releases Project. A couple of weeks later, I was appointed the new Lead of the OpenJDK 11 Updates Project. This is an important milestone in the history of OpenJDK and of Java SE because it’s the first time that a non-Oracle employee has led the current long-term OpenJDK release project. JDK 8 is still a much-used Java release in industry, and JDK 11 is the current long-term maintenance release. It’s now a couple of weeks after the first releases of JDK8u and JDK11u on my watch. I think the process went pretty well, although it was not entirely smooth sailing for the developers. Having said that, we got our releases out on the day, as planned, and so far we’ve seen no major problems. Read more

How to advance your career by contributing to open source projects

In 2017, I wrote my (so-far) most popular article of all time, "The Impact GitHub is Having on Your Software Career, Right Now…," on Medium. In that article, I cast the vision for how you can develop your career through open source contributions. It clearly struck a nerve—it got 382 points and 237 comments on Hacker News. Many of the comments hated on it so hard—they disagreed with my main premise—but I felt they had missed the point. At the time I was a recruiter with 10 years of engineering experience, working at Red Hat. There is nothing I love more than a challenge, so I went "deep cover." I quit my job as a recruiter and got a job as a software engineer in a pure closed-source company that uses BitBucket and has PCI-compliant security. Fourteen months later, I got hired by Camunda to work as the developer advocate for Zeebe, a workflow engine for orchestrating microservices, purely based on my open source contributions while working at that job. I just did everything I advised readers to do in the comments of my original Medium article. Read more