Fedora 37 Planning For Binutils 2.38, GNU C Library 2.36

[phoronix]

Phoronix: Fedora 37 Planning For Binutils 2.38, GNU C Library 2.36

It should be hardly surprising at all for longtime Linux users aware of how Fedora Linux tends to always ship with the most modern open-source compiler toolchain support possible, but for Fedora 37 this autumn they again are planning for the latest and greatest...

https://www.phoronix.com/scan.php?page=news_item&px=Fedora-37-Toolchain

[_ReD_]

The planned GNU toolchain for Fedora 37 can be found via this change proposal as mostly a formality given Fedora's history of bleeding edge toolchain support.

I'd object to this characterization. Fedora is cutting edge at most. The bleeding edge is beta—half broken stuff. Fedora is more conservative than that.

[torsionbar28]

I'd object to this characterization. Fedora is cutting edge at most. The bleeding edge is beta—half broken stuff. Fedora is more conservative than that.

x2, Fedora is intended for stable daily driver use. It isn't a beta/experimental distro at all.

[pWe00Iri3e7Z9lHOX2Qx]

x2, Fedora is intended for stable daily driver use. It isn't a beta/experimental distro at all.

Agreed, although how current it manages to stay without being a rolling distro may surprise some people.

Just for fun, this is from my Fedora workstation right now.

rpm -qa | grep -E '(plasma-desktop-[0-9]|kernel-core|mesa-vulkan|glibc-[0-9])' | sort

glibc-2.35-12.fc36.x86_64
kernel-core-5.18.9-200.fc36.x86_64
mesa-vulkan-drivers-22.1.2-1.fc36.x86_64
plasma-desktop-5.25.2-1.fc36.x86_64

And this is from a Manjaro VM (on the 5.18 series kernels).

sudo pacman -Syyu
[sudo] password for nuke:
:: Synchronizing package databases...
core 167.3 KiB 183 KiB/s 00:01 [################################################## #############] 100%
extra 1861.7 KiB 2.16 MiB/s 00:01 [################################################## #############] 100%
community 7.0 MiB 8.18 MiB/s 00:01 [################################################## #############] 100%
multilib 175.6 KiB 1228 KiB/s 00:00 [################################################## #############] 100%
:: Starting full system upgrade...
there is nothing to do


pacman -Q | grep -E '(plasma-desktop|linux[0-9]|^mesa |^glibc )' | sort

glibc 2.35-6
linux518 5.18.7-1
mesa 22.1.2-1
plasma-desktop 5.24.5-2

Yes, Fedora 36 seems to have upgraded to Plasma 5.25.x before Manjaro. Of course Arch proper is on 5.18.9 and Plasma 5.25.2 like Fedora, but with the even newer Mesa 22.1.3 that was released last Thursday.

[RahulSundaram]

Yes, Fedora 36 seems to have upgraded to Plasma 5.25.x before Manjaro. Of course Arch proper is on 5.18.9 and Plasma 5.25.2 like Fedora, but with the even newer Mesa 22.1.3 that was released last Thursday.

Incidentally both KDE and kernel that you cite is in the exception list specifically so that they can track upstream more closely but even otherwise, Fedora maintainers can largely maintain the packages as they see fit and it is easier to rebase than backport fixes, so that's what ends up happening in many situations. Effectively, updates look like a hybrid of rolling release and a traditional release in practice.

[pWe00Iri3e7Z9lHOX2Qx]

Incidentally both KDE and kernel that you cite is in the exception list specifically so that they can track upstream more closely but even otherwise, Fedora maintainers can largely maintain the packages as they see fit and it is easier to rebase than backport fixes, so that's what ends up happening in many situations. Effectively, updates look like a hybrid of rolling release and a traditional release in practice.

Indeed. Fedora manages to stay so current that "I want the new stuff!" isn't necessarily a great reason to opt for a rolling release instead. My Tumbleweed install got a 3 week head start on Plasma 5.25, but Fedora has more polish and way fewer paper cuts out-of-the-box.