At the same time Oracle started requiring a subscription for Oracle JDK use in production environments. Some packages have now been taken over by others, but he still recommends not building packages that rely on Java as "it's a house of cards waiting to come down." Eclipse, he said, is "almost impossible to package" because it "uses its own build system (tycho), leading to a bootstrap problem," and is "really sensitive to minor changes in its dependency tree.In the beginning of 2019 Oracle stopped releasing free-of-charge updates to their JDK, except for personal use. Valentini said they were in good shape for Fedora 33, but that in mid-2020 contributions dwindled and stopped, leaving him with an unmanageable burden. This turned out to be wrong, thanks to "numerous technical issues," so the Java packages were revived and Valentini and others stepped up to help. In 2019 the original maintainer of Fedora Java packages orphaned them, believing that modularity, which lets maintainers bundle specific major versions of packages with an application, would make them unnecessary. The key issue concerns packages such as LibreOffice and Eclipse that depend on Java software other than the JDK (Java Development Kit). He also emphasised that while he has dropped maintaining the Java packages, he remains primary maintainer for some 245 other packages "that I'm happy to keep." The OpenJDK packages themselves are well-maintained." Updated at 13.04 BST to addįollowing publication of this article, Valentini got in touch to expand on his concerns, and explained to The Reg that: "What I refer to as 'Java packages' is only software written in Java – or another language targeting the JVM – but this does not include the OpenJDK packages. Leaving that aside, Fedora 34 worked smoothly and looked good in our first try with the new release. Java will of course still run fine on Fedora but this is a warning flag for those relying on the supplied packages. Java is of critical importance in RHEL thanks to its use for many enterprise applications, and it is the third most popular programming language according to a recent survey. There is something alarmingly Windows-like in the way Fedora Workstation demands to be rebooted to install OS updates Cotton has said that he is "starting the conversation about how to prevent this in the future." Of these, the introduction of GNOME 40 will be the most visible to users, and the switch to PipeWire should improve audio handling significantly.įedora program manager Ben Cotton revealed yesterday that Release Candidate (RC) 1.2 was approved for final release today – though the speed of the approval, with just five hours between the completion of the RC and the meeting to approve it, has caused concern. The desktop is GNOME 40, described by Fedora project leader Matthew Miller as "the first time since GNOME 3.0 came out that there's a real rethinking of the basic desktop experience.".Wayland will be used by default for KDE editions of Fedora (it is already the default for GNOME).The LLVM toolchain is updated to version 12 with all its sub-projects - The Ruby language is updated from 2.7 to 3.0, and the Ruby on Rails framework to 6.1.For audio, PipeWire will be used instead of PulseAudio and JACK - Systemd-oomd, which aims to mitigate out of memory conditions, will be on by default. btrfs (B-tree file system), which has been the default for Fedora Workstation since Fedora 33, will now have transparent zstd (Zstandard) compression. What is new in Fedora 34? The full list of changes is here and includes: Updated Fedora 34, a feature-packed new release of Red Hat's leading edge Linux distribution, was released today, though the main Java package maintainer has quit, urging "affected maintainers to drop dependencies on Java."įedora 34 is used by Red Hat to try out new features that are likely to end up in first CentOS Stream and then Red Hat Enterprise Linux (RHEL), the commercial offering.
0 Comments
Leave a Reply. |