bc97c3aa53
This patch teaches `db list` to also use the pkglist metadata when it can, just like we did for `db diff`. To spell it out: this then allows `db list` to work on commits for which we only have the commit object. I went for the surgical incision here and didn't try to support invocations which use fnmatch patterns for now. Definitely possible, though it didn't feel like it was worth the effort given that the common case is just a raw `db list` (I'd wager most people are probably hard-wired to pipe to `grep` anyway for filtering). Also fix the usage string, which had the arguments flipped. Closes: #1299 Approved by: cgwalters |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose-tests | ||
| composedata | ||
| ex-container-tests | ||
| gpghome | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose | ||
| ex-container | ||
| README.md | ||
Tests are divided into three groups:
-
Tests in the
checkdirectory are non-destructive and uninstalled. Some of the tests require root privileges. Usemake checkto run these. -
The
composechecktests currently require uid 0 capabilities - the default in Docker, or you can run them via a user namespace. They are non-destructive, but are installed.To use them, you might do a
make && sudo make installinside a Docker container.Then invoke
./tests/compose. Alternatively of course, you can simply run the tests on a host system or in an existing container, without doing a build.Note: This is intentionally not a
Makefiletarget because it doesn't require building and doesn't use uninstalled binaries. -
Tests in the
vmcheckdirectory are oriented around using Vagrant. Usemake vmcheckto run them. See alsoHACKING.mdin the top directory.
The common directory contains files used by multiple
tests. The utils directory contains helper utilities
required to run the tests.