Fedora / Red Hat / IBM Leftovers

posted by Roy Schestowitz on Oct 07, 2022

• CPE Weekly Update – Week 40 2022 - Fedora Community Blog

  This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat.

  We provide you both infographics and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

• Telecompaper: NEC selects Red Hat OpenShift as preferred container platform for mission-critical applications

• Red Hat CEO on OpenShift roadmap, competitive play

  Red Hat’s newly minted CEO Matt Hicks talks up OpenShift’s roadmap, the competition with VMware and opportunities in the Asia-Pacific region.

• 3 ways CIOs can empower their teams during uncertainty

  The role of the CIO has evolved from technology decision-maker and IT gatekeeper to change agent and strategic business partner, influencing decisions that impact client and customer-facing business initiatives. In addition to serving as technology experts who lead the traditional enterprise IT organization, CIOs now lead collaborative, cross-functional initiatives that drive business impact.

  Additionally, CIOs must be change leaders, driving innovation and business agility at scale. In times of economic volatility, CIOs, more than ever, are tasked with helping organizations ride out the storm.

• Moving from apt to dnf package management

  A package manager makes it simple to install GNU/Linux applications on a local computer. Before package management became commonplace, installing applications was a tedious, error-prone undertaking. The ease a package manager brings to installing an application on a Linux computer has been a major factor contributing to the widespread adoption of Linux as a mainstream operating system for both business and home users.

• What's inside an RPM .repo file?

  The previous article in this series, How does RPM package discovery work?, described how the RPM package management technology discovers and installs an .rpm package on a local computer running the Red Hat Enterprise Linux, Fedora, or CentOS Stream operating system. In that article, you learned that the .repo files stored in the /etc/yum.repos.d directory of the local machine play a critical role in discovering, installing, and managing RPM packages.

  This article goes to the next level of detail to describe the format specified for a .repo file.

  This article describes not only the format specification for a .repo file but also describes the logic that's applied to a .repo file when managing RPM packages on a given machine. But, before delving in, let's review how RPM discovers a package on the internet and then installs it.