https://bugzilla.redhat.com/show_bug.cgi?id=1594378 --- Comment #4 from Neal Gompa <ngompa13@xxxxxxxxx> --- (In reply to Dusty Mabe from comment #3) > (In reply to Neal Gompa from comment #2) > > Simple question, why are you regenerating the entire spec file every time > > for ignition with gofed? For snapd, I just use gofed to update the > > BuildRequires and Provides list. Generally, the rest of the spec doesn't > > change much. > > yeah. i'm a bit of a noob with go packaging. I tend to regenerate the spec > into a new file then vimdiff the old .orig and .spec file to see what I > changed last time. Then add those changes to the new spec I created and > check it all in (new .orig and new .spec). is there another command you use > other than `gofed repo2spec` ? I use repo2spec too, only because the aspect I want hasn't been broken out into a subcommand yet. But I just copy the Provides: lines and overwrite them in my spec file every time. It's not terribly difficult and because the rest of the spec rarely changes, it's pretty easy. In your case, you don't even really have to do BR checking, since you're using bundled dependencies (snapd is fully unbundled for Fedora). -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx/message/73GADGQ3CUN7UXM3PHAMRAYS7QI55WG3/
