lspkg [-f |-F |-s |-n |-p |-k |-K]   [-d |-D |-i |-m |-r]   [-c |-t]   [--status]   PROFID LIST [any options]
lspkg --help  |--version

lspkg reads packages list, given in argument LIST, and outputs corresponding packages to stdout. It can be names of the same packages in other form (binary archives), or names of dependencies for given package set, or both.
By default it prints plain package names from lists without modifications, like lsrdd(1) does.

lspkg reads configuration data from rdd(1) configs, so configuration needs to be assigned in argument PROFID. Configuration data keeps the location of lists and default list name.

Syntax of arguments and possible key=value options are the same, as for commands of main any(1).

lspkg loads shell environment of other packages to read their dependencies. So KEYWORDS and use-flags affect the output.

Print mode

-f

Print names of binary archives, which would come after the build with current configuration.

-F

Print full names of binary archives with absolute path, which actually exist in current package directory. any_pkg=path option can change the default in-engine package location.

-s

Print short names without version.

-n

Print names of package, as it declares in build file. There would be difference with -p mode, if package had changed its P, PN, PV inside build file.

-p

Print plain names from text lists. The default mode.

-k

Print key-value pairs: plain package name and verified relative path to binary archive of the package.

-K

Print key-value pairs: plain package name and verified absolute path to binary archive of the package.

Dependencies

-m

Print direct build dependencies of given package set. Tree is not calculated.
CMD arguments are not printed, so the output contains only dependencies.
Only non-deployed packages are printed.

The mode can be used to detect minimal set of dependencies, needed for deployment, so that given packages can be built.

-i

Print direct build dependencies of given package set. Tree is not calculated.
CMD arguments are not printed, so the output contains only dependencies.
Both deployed and non-deployed packages are printed.

The mode can be used for deployment of all packages for given set.

-D

Print entire recursive tree of build dependencies for given package set.
CMD arguments are included.
Both deployed and non-deployed packages are printed.

The mode can be used for mass rebuilding from scratch, needed for given set.

-d

Print recursive tree of build dependencies for given package set.
CMD arguments are included.
Only non-deployed packages are printed.

The mode can be used for minimal rebuilding, needed to build the given set.

-r

Print reverse dependencies for given package set: the packages which depend on given set. This is used to determine the impact of given packages on others.

-t

Resolve direct build dependencies of given package set. Tree is not calculated.
Then print each dependency, followed by the packages from given set, that directly depend on it.

All other options are ignored in this mode.
Option requires the usage of temporary file.

Other

-c

Check the correctness of list order for each given package.
Correct order means all packages must be placed in list after their dependencies.
If incorrect order is detected, return non-zero code.

All other options are ignored in this mode.
Option requires the usage of temporary file.

--status

Print plain package name, build status and time of build.
Used in distributed builds.

--

Stop processing options.

--version

Print version and exit with 0 code.

--help

Print short help description and exit with 0 code.

any(1), any-howto(7), lsrdd(1)