On 04. 12. 19 19:01, Shawn Wells wrote:
On 11/28/19 8:18 AM, Matěj Týč wrote:
> Hello everybody,
> recently, the 5000th PR  of the ComplianceAsCode project landed,
> proposing the Packit CI support. Packit uses the Fedora spec file
> , i.e. source of the RPM package, in the test process.
Does the conversation need to go beyond "default to open"?
Here is a small update of what Packit can / can't do as of January 2020:
* The spec file synchronization would only apply to rawhide spec
files, which is not what general public comes in touch with.
* Packit CI doesn't work with spec files that reference other files
from dist-git, s.a. patches.
In other words, the current purpose of Packit CI is verification whether
a package can be built on Fedora, and there is a risk of false positives
- different Fedora versions may require different spec files in order to
build, which Packit can't handle ATM.
I see no benefit to expose Rawhide spec file in the upstream project,
and I am against exposing it for modification to people who may not have
gotten familiar with Fedora packaging guidelines and that themselves
can't propose Fedora updates.