Fedora Account System
Red Hat Associate
Red Hat Customer
Spec URL: https://raw.githubusercontent.com/dustymabe/ignition-rpm/3aca3a9c2a2ba806b4b2cfb8746b8f10a52bece3/ignition-dracut.spec SRPM URL: https://kojipkgs.fedoraproject.org//work/tasks/387/27790387/ignition-dracut-0-0.1.gitbf3b454.fc29.src.rpm Description: dracut modules to enable ignition services to run in the initramfs This package includes files that enable ignition to run in the initramfs on systems. I broke this out into a separate package from ignition because - a user could be grabbing the ignition rpm just to validate configs - running through gofed often and adding a subpackage afterwards is a pain right now it pulls from a repo on github called dustymabe/bootengine. I'm planning to rename that repo to ignition-dracut, but have an open PR I'd like to get merged before I do that. The review for the ignition main rpm is here: https://bugzilla.redhat.com/show_bug.cgi?id=1576879 koji scratch build is here: https://koji.fedoraproject.org/koji/taskinfo?taskID=27790386 Fedora Account System Username: dustymabe
Taking this review.
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.
(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` ?
(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).
(In reply to Neal Gompa from comment #4) > > 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. Yeah I guess that's essentially what I'm doing too, but with an extra layer of "vimdiff" in there to make sure nothing else changed. Probably not needed.
It was requested that I add ignition-dracut as a subpackage of ignition instead of a separate package. See https://bugzilla.redhat.com/show_bug.cgi?id=1576879#c16
*** This bug has been marked as a duplicate of bug 1576879 ***