Built: over 2 years ago
Size: 698 KB
Home page: http://www.rpm.org/
Summary: The RPM package management system
The RPM Package Manager (RPM) is a powerful command line driven
package management system capable of installing, uninstalling,
verifying, querying, and updating software packages. Each software
package consists of an archive of files along with information about
the package like its version, a description, etc.
List of contributors:
Merged 4.0.4-alt101.M80P.7 into p7, t7 (by Vladimir D. Seleznev). - Dropped %_allow_deps_with_beginning_dot support (introduced in 4.0.4-alt100.76.M70C.3).2019-03-14 Ivan Zakharyaschev 4.0.4-alt100.77.M70P.4.1
[rpmbuild changes up to 4.0.4-alt128] - Dropped $RPM_STRICT_INTERDEPS support (introduced in 4.0.4-alt100.76.M70C.2). - Changed the generator of package self-provides and the generator of strict intersubpackage dependencies to use [E:]V-R[:D] format instead of [E:]V-R (by Vladimir D. Seleznev and Dmitry V. Levin). - For stable branches (like p8, c8), made the generator of package self-provides additionally produce [E:]V-R (for compatibility with old rpm and apt). - Make "new" packages (with disttags) be treated better by the "old" disttag-unaware rpm in some cases; primarily those with < and/or > Conflicts on another subpackage. This form of Conflicts is used to ensure that no subpackages from different releases/builds get installed together. (A better way to express this is to add a common subpackage that all other subpackages depend on.) This change doesn't affect the way the "new" rpm would treat packages with such deps (ALT#35930): + rewrite < and > dependencies so that they have almost the same meaning when treated by old disttag-unaware tools; - build/reqprov.c: made addReqProv() aware of the disttag of the package.2019-03-14 Ivan Zakharyaschev 4.0.4-alt100.77.M70P.3.3
Merged 4.0.4-alt101.M80P.5.2 into p7, t7: [rpm] - Changes in what is considered "newer" by rpm -U pertaining to disttag comparison. (On the whole, to determine which package is "newer", first, the EVRs are compared, then the branch prefixes of the disttags if the disttags are present, and then the buildtimes.) The comparison of the disttags: + (new!) If a disttag contains no + separator (old format), the branch prefix is assumed to be empty (and hence "older" than any other branch prefix). + (new!) If the branch prefix of a disttag is equal to %_priority_distbranch (and it is not empty), then it is "newer" than any other ones. + (as before, since 4.0.4-alt101.M80P.5) The branch prefixes of disttags are ordered lexicographically. - (disabled in this release; %if_enabled default_priority_distbranch) Give a default value to %_priority_distbranch based on the disttag when this package is built (the prefix before +).