Hello everybody,
recently, the 5000th PR [1] of the ComplianceAsCode project landed,
proposing the Packit CI support. Packit uses the Fedora spec file [2],
i.e. source of the RPM package, in the test process.
The discussion in that PR centered around handling of the spec file - it
now became possible to have it in the repository, syncing it with the
Fedora server, or Packit would pull it from the Fedora repository
whenever it is needed. Both ways have theirs pros and cons, and as you
can read in [1], some members of the community raised concerns that the
current way of how the spec file is handled encumbers the community.
So if this is also your case, please let us know how having the spec
file upstream would change the situation for you. For the sake of
completeness, nowadays we update the package every time we make an
upstream release, and we issue a build and respective update right after.
References:
[1]:
https://github.com/ComplianceAsCode/content/pull/5000
[2]:
https://src.fedoraproject.org/rpms/scap-security-guide/blob/master/f/scap...