From the course: Building, Maintaining, and Distributing RPM Packages

Unlock this course with a free trial

Join today to access over 22,600 courses taught by industry experts.

Modifying source with patches

Modifying source with patches

- [Instructor] While you can think of binary packages as sort of flattened, representing only the result of building a package, source packages can contain layers of code, allowing you to preserve original source code and then make changes to it over time with patches. While thinking about layers of changes is not uncommon to those of us who are familiar with source control systems like Git, the way we track code changes over time in packages is a little different. To make changes to code but preserve the historical source, we use patches, which are files that represent targeted changes to existing code. Patch files represent differences between an earlier state of code and the desired state. Let's say we want to make a change to the software we've been working with so far. Of course, we could go edit the original file. But then when we look back at the package in the future, the original code would have been lost. Instead we…

Contents