The tool is a "web front-end" for the command line utilites
that are used for reviewing the meta information of the
available software. You may well use those tools in your own
terminal to see this information related more exactly to your
own system, whereas here you’ll see it related to "all"
possible installations in union.
When you inspect the web front-end in more detail, you will find
that the "Package pattern:" phrase is actually a selection
toggle where you can choose between that and "File pattern:".
The former uses the pattern as argument to
policy and brings up the result of that, and the
latter instead uses the pattern as argument to
and brings up the result of that. Note that both of the search
types are time limited and that if the pattern is too generic,
it results in a search timeout response.
policy-query result includes onwards links from
the version code elements as
with the particular package and version as argument. This runs
show followed by an
and presents the result of that with dependent package names set
out as links to further
package-query result also includes a "debtree"
button for reviewing the package dependencies using
When the selection toggle says "File pattern:", the tool will
find with the pattern as argument (instead of
and present the result of that. This has similar onwards links
policy-query requests for the package names.
Note that all results are heavily flavoured by the backend
setup. The servicing host has a source list that includes all
(and only) current Devuan points for the architectures
while it is an
amd64 itself. In some cases it helps
to add, e.g., ":arm64" to the end of the pattern so as to focus
the search on that architecture, but it's of course up to
the backend command as to whether that is useful.