On Fri, Sep 25, 2020 at 02:30:32PM -0400, Mark Mielke wrote: > On Fri, Sep 25, 2020 at 4:35 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> > wrote: > > > If you have the tarball you can trivially generate the source RPM if > > you need it because the tarball still contains the .spec file. IOW > > just run > > > > $ rpmbuild -ts libvirt-6.7.0.tar.xz > > Wrote: /home/berrange/rpmbuild/SRPMS/libvirt-6.7.0-1.fc32.src.rpm > > > > I've never tried this before... what does it do if the .spec file is > non-trivial and includes things expanded by autoconf, or if there are > multiple different .spec files? It only works when there is a single .spec file, which is the case with libvirt tarballs. Expansion of macros is largely irrelevant until you get the build stage. > Personally, I have found the libvirt provided spec file limiting - and use > a distro one like Fedora as a starting point instead. Errm, the libvirt.spec inside the tarball *IS* the Fedora distro spec. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
