2026-01-20 08:31:50
RE: #Fedora 💕 :fedora:
Using “AI” to manage your #Fedora system seems like a really bad idea
https://www.osnews.com/story/144006/using-ai-to-manage-your-fedora-system-…
J'ai publié la note « Setup Fedora CoreOS avec LUKS et Tang »
#Fedora
I have been trying for YEARS to have my printer print on Linux and it has always felt like a headache and I stopped before it worked.
Today, having no other choices, I plugged it in my #Fedora Silverblue 43. A pop-up asked me for my admin creds. I inserted it. VoilŠ. The printer works and I had nothing to do for it to work. That's amazing 😻 Whoever fixed this and automated this: you are…
Hey #Fedora community. A friend of a friend is looking for a Fedora10 pin and/or a sticker or some other merch with the Fedora10 branding on it. Can you help me with that? I know 2008 was ages ago:)
:fedora: The fact #LinusTorvalds recommends #Fedora, make me smile!
#Linux
After #LinusTorvalds recommending #Fedora, I would recommend you to check out #secureblue!
There should be a policy that when a package provides multiple build systems for itself, and you're building it with #CMake, you should always remove all installed CMake files to make software developed on your platform portable.
#Debian #Fedora #Gentoo #packaging
Barely three hours later, I found myself back on my #secureblue desktop.
⭐ #FedoraAtomic
According to #FreePG right now: #ArchLinux, #Debian, #Fedora, #NixOS and #Ubuntu. Now #Gentoo joins that list, except that instead of silently making intrusive patching on top of GnuPG, we provide it as a separate package (app-crypt/freepg), and mark appropriately:
$ gpg --version
gpg (GnuPG) 2.5.13-freepg
Another post on #Quansight PBC blog: "BLAS/LAPACK #packaging"
#BLAS and #LAPACK are the standard libraries for linear algebra. The original implementation, often called Netlib LAPACK, developed since the 1980s, nowadays serves primarily as the origin of the standard interface, the reference implementation and a conformance test suite. The end users usually use optimized implementations of the same interfaces. The choice ranges from generically tuned libraries such as OpenBLAS and BLIS, through libraries focused on specific hardware such as Intel® oneMKL, Arm Performance Libraries or the Accelerate framework on macOS, to ATLAS that aims to automatically optimize for a specific system.
The diversity of available libraries, developed in parallel with the standard interfaces, along with vendor-specific extensions and further downstream changes, adds quite a bit of complexity around using these libraries in software, and distributing such software afterwards. This problem entangles implementation authors, consumer software authors, build system maintainers and distribution maintainers. Software authors generally wish to distribute their packages built against a generically optimized BLAS/LAPACK implementation. Advanced users often wish to be able to use a different implementation, more suited to their particular needs. Distributions wish to be able to consistently build software against their system libraries, and ideally provide users the ability to switch between different implementations. Then, build systems need to provide the scaffolding for all of that.
I have recently taken up the work to provide such a scaffolding for the Meson build system; to add support for BLAS and LAPACK dependencies to Meson. While working on it, I had to learn a lot about BLAS/LAPACK packaging: not only how the different implementations differ from one another, but also what is changed by their respective downstream packaging. In this blog post, I would like to organize and share what I have learned.
"""
#CondaForge #Debian #Fedora #Gentoo