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 |
||
|---|---|---|
| .. | ||
| data | ||
| Makefile.am | ||
| README.md | ||
| atlocal.in | ||
| local.at | ||
| rpmbuild.at | ||
| rpmbuildid.at | ||
| rpmconfig.at | ||
| rpmconfig2.at | ||
| rpmconfig3.at | ||
| rpmconflict.at | ||
| rpmdb.at | ||
| rpmdepmatch.at | ||
| rpmdeps.at | ||
| rpme.at | ||
| rpmgeneral.at | ||
| rpmi.at | ||
| rpmio.at | ||
| rpmmacro.at | ||
| rpmorder.at | ||
| rpmpgp.at | ||
| rpmpgpcheck.c | ||
| rpmpython.at | ||
| rpmquery.at | ||
| rpmreplace.at | ||
| rpmscript.at | ||
| rpmsigdig.at | ||
| rpmspec.at | ||
| rpmtests.at | ||
| rpmvercmp.at | ||
| rpmverify.at | ||
| rpmvfylevel.at | ||
README.md
To run these tests, you need at least these dependencies on the host:
- fakechroot
- gdb
- gnupg >= 2.0
Then run the command
make check
The number of tests performed depends on features enabled at configure time,
at least --with-/--without-lua and --enable-/--disable-python.
See also the INSTALL file for more information.
To run single tests, you can run the commands:
make populate_testing && ./rpmtests $NNN $MMM ...
where NNN and MMM are the numbers of the tests to be run.
To get the list of available tests, use the command:
./rpmtests -l
You can also select tests by keywords used in their description by using the command:
./rpmtests -k $KEYWORD
Use multiple -k parameters to have tests with different keywords run.
Use -k $KEYWORD1,$KEYWORD2 to execute tests matching both KEYWORD1 and KEYWORD2.
See the output of the command:
./rpmtests --help
for more options. But be aware some (like -j) need not work properly with
the test suite unless a very restricted set of test is run.