On Wed, Feb 22, 2023 at 08:12:01PM +0000, Mattia Verga via devel wrote:
So, does that mean that every time a compose is performed pungi
downloads all RPMs tagged with a specific tag in a directory and then it
operates on those to create repository metadata? Or it just downloads
the rpms headers, or whatever?
Yes. It downloads them all, because it needs the ones signed with the
specific keys in it's config. It can optionally however look at a
previous config and decide that nothing changed in koji so it can reuse
them, but in practice I think this doesn't happen much.
Can we have a persistent compose root directory as base, then
the latest builds (if newer), do the pruning "based on something",
create the repo and save the state as the base for the next run? Or will
that eat way too much disk space? On the other hand we could save
bandwith because we would not download all the rpms which were not
updated from the previous run... what's more valuable for our
infrastructure, disk space or network bandwith usage?
Definitely disk space is more important right now.