The RPM package management system
%{name} and %{version} refer to the name and version strings of the
package that will be built and shouldn't be used for things that
do not honor those macros. Such as pre-existing or predetermined
filenames.
De-facto packaging practises over multiple decade liberally (ab)use
these and various other macros in places they don't belong - if rpm itself
doesn't follow its own rules then how can we expect anybody else to do so...
This doesn't change anything as is, but enables both Name: and Version:
to be changed arbitrarily without breaking the package build, which is
how it should optimally be. If this was strictly followed then scl-utils
would've been a walk in the park. Relatively speaking.
|
||
|---|---|---|
| .gitignore | ||
| 0001-Don-t-look-into-source-package-provides-in-depsolvin.patch | ||
| 0001-find-debuginfo.sh-decompress-DWARF-compressed-ELF-se.patch | ||
| 0001-Fix-regression-causing-all-ELF-files-classified-as-O.patch | ||
| 0001-Revert-Improve-ARM-detection.patch | ||
| 0001-rpmfc-Do-not-prepend-buildroot-to-a-path-for-paramet.patch | ||
| 0001-Unset-SOURCE_DATE_EPOCH-for-the-test-suite.patch | ||
| 0001-Warn-on-undefined-components-in-buildtree-macros.patch | ||
| rpm-4.7.1-geode-i686.patch | ||
| rpm-4.9.90-no-man-dirs.patch | ||
| rpm-4.12.0-rpm2cpio-hack.patch | ||
| rpm-4.15.x-ldflags.patch | ||
| rpm-4.15.x-siteconfig.patch | ||
| rpm.spec | ||
| rpmdb-rebuild.service | ||
| sources | ||
| STAGE2-rpm | ||