Outils de développement
To observe what a program is doing, Fedora provides additional meta-data about code that is installed and runs on your system. These can be used together with tracers, profilers and debuggers to better understand what is running on your system (or to understand crashes or failures better). Previously, these debug info meta-data packages were fairly large, containing lots of information about multiple sub-packages together. With Fedora 27, these debug info meta-data packages have been split up into smaller sub-packages, making it possible to install just the debuginfo for one specific sub-package or library. The source files needed for debuggers (but not necessarily for tracers and profilers) have been separated out into their own debugsource package and it is now possible to install multiple, different versions or architectures of the debug info packages at the same time. For example, when trying to introspect a program installed in a container or virtual machine that is a different version of the package installed on the host, or when both a 32 bit and 64 bit version of a library is available.
Support for updating non-RPM artifacts, like modules.
Support for complex package dependencies, which enables Fedora to start packaging Rust packages and allows Fedora to do a better job expressing valid ranges of supported dependency versions for existing packages.
Support, via Pungi, for generating OSTrees that are more consistent with Fedora’s release day OSTrees.
Want to help? Learn how to contribute to Fedora Docs ›