One of the maintenance tasks of an RMT server is to find potentially stale repositories. This can be done as shown in issue #1136. One could parse the rmt-cli mirror [args] output, to get a list of "active" repositories. Everything else is potentially stale.
It would be nice to have an API to query the download locations. Perhaps as additional column in the rmt-cli repos [custom] list --cvs output. This removes to the need to parse a logfile to find the same information. In the end, rmt-cli already knows upfront where repository content will be stored.
One of the maintenance tasks of an RMT server is to find potentially stale repositories. This can be done as shown in issue #1136. One could parse the
rmt-cli mirror [args]output, to get a list of "active" repositories. Everything else is potentially stale.It would be nice to have an API to query the download locations. Perhaps as additional column in the
rmt-cli repos [custom] list --cvsoutput. This removes to the need to parse a logfile to find the same information. In the end, rmt-cli already knows upfront where repository content will be stored.