standard CI packages files

[Yedidyah Bar David]

Hi all,

The various automation/*.packages* files are rather hard to maintain -
with many partial duplicates, symlinks, and changes applied to some
file forgotten to be applied to others that needed them.

Can we have something more dynamic? E.g. that CI will run a single
script, e.g. automation/get-needed-packages, provide it as args the
action to be ran ("check-patch", "build-artifacts" etc.) and the
distro ("el7", "fc27" etc.) and use whatever it outputs as the list of
packages to install?

Thanks,
-- 
Didi