122bb4ffae
The trend of packaging is to hide more and more of what actually happens behind helper macros and other dynamically generated constructs. While this is mostly a good thing, it makes understanding and postmortem analysis harder than it should be. Add the spec in its parsed and expanded form into the src.rpm header to make the actual contents of the build more trackable. It can be argued this does not belong in the header and should be in payload instead, my rationale for the placement is that this way the payload remains effectively arch independent, whereas the header already heavily reflects the particular environment where it was built. Probably worth noting that %setup and %patch built-in macros are not properly expanded in the stored spec, but that's a separate issue related the special way %prep is processed. Fixes: #1241 |
||
---|---|---|
build | ||
ci | ||
docs | ||
fileattrs | ||
include/rpm | ||
lib | ||
misc | ||
plugins | ||
po | ||
python | ||
rpmio | ||
scripts | ||
sign | ||
tests | ||
tools | ||
.gitignore | ||
.mailmap | ||
CHANGES | ||
CONTRIBUTING.md | ||
COPYING | ||
CREDITS | ||
INSTALL | ||
Makefile.am | ||
Makefile.maint | ||
README | ||
autogen.sh | ||
cliutils.c | ||
cliutils.h | ||
configure.ac | ||
debug.h | ||
installplatform | ||
macros.in | ||
mkinstalldirs | ||
platform.in | ||
rpm.am | ||
rpm.c | ||
rpm.pc.in | ||
rpm2archive.c | ||
rpm2cpio.c | ||
rpmbuild.c | ||
rpmdb.c | ||
rpmkeys.c | ||
rpmpopt.in | ||
rpmrc.in | ||
rpmsign.c | ||
rpmspec.c | ||
system.h |
README
This is RPM, the RPM Package Manager. The latest releases are always available at: http://rpm.org/releases/ Additional RPM documentation (papers, slides, HOWTOs) can also be found at the same site: http://rpm.org. http://rpm.org/community all rpm releated mailing lists. RPM was originally written by: Erik Troan <ewt@redhat.com> Marc Ewing <marc@redhat.com> See the CREDITS file for a list of folks who have helped us out tremendously. RPM is Copyright (c) 1998 by Red Hat Software, Inc., and may be distributed under the terms of the GPL and LGPL (see the file COPYING for details).