On Thu, Jan 31, 2019 at 08:37:14AM -0500, Frediano Ziglio wrote: > > On Thu, Jan 31, 2019 at 10:34:27AM +0000, Frediano Ziglio wrote: > > > Having the RPM spec file produced by the build is helpful in > > > different situation. Different tools like mock or code > > > scanners accept source RPMs as input. > > > Providing this file allows easily build of the source RPM (and > > > binaries) using a simple command like > > > > > > $ rpmbuild -ta spice-protocol-XXXX.tar.bz2 > > > > > > The spec proposed is a port of current Red Hat spec combining with > > > MingW one which allows to build MingW packages easily with a > > > > > > $ rpmbuild --with mingw -ta spice-protocol-XXXX.tar.bz2 > > > > > > Signed-off-by: Frediano Ziglio <fziglio@xxxxxxxxxx> > > > > Are you planning to push for this file to be used for RHEL/fedora > > builds? Or is this going to be a 3rd spec file to maintain? > > > > Christophe > > > > It would be great to have a single one. > I don't know if this is technically possible and how to do it. > I think fedpkg requires to have the spec in the git repository, > I suppose we can say to copy and save from the project repository > one. I'm not asking that fedpkg gets the .spec file from the tarball and use that, I'm merely asking if you have plans to unify the file used in fedora/rhel and in the tarball. It's fine with me if the same file is committed to 3 different places (upstream git, fedora dist-git, rhel dist-git). I'm less fine with these 3 spec files being maintained separately with arbitrary differences. Christophe
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel