https://bugzilla.redhat.com/show_bug.cgi?id=1169966 --- Comment #21 from Lokesh Mandvekar <lsm5@xxxxxxxxxx> --- (In reply to Tom "spot" Callaway from comment #20) > 1) Add a README.fedora that points to the latest Fedora image and let the > user figure it out AND/OR Include a script to download the latest Fedora > image (but don't run it in a %post scriptlet please). If I'm reading this right, this option still _does not_ allow me to include the fedora image in the srpm but leave it to the user to fetch it, correct? If that is the case, this probably won't be doable. > 2) Somehow get the latest Fedora image into an RPM where the corresponding > SRPM has the BuildRequires to properly build it from the RPMs in the Fedora > tree, then Requires on that image RPM here. (This sounds convoluted, and it > is, but it ensures that we are in license compliance). Does this involve building the fedora docker base image from scratch in the other rpm (something like http://koji.fedoraproject.org/koji/taskinfo?taskID=8289768 ) or can I simply add the image tarball in the other rpm? -- 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 https://admin.fedoraproject.org/mailman/listinfo/package-review