[Bug 1169966] Review Request: rocket - CLI for running app containers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1169966



--- Comment #22 from Tom "spot" Callaway <tcallawa@xxxxxxxxxx> ---
(In reply to Lokesh Mandvekar from comment #21)

> 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.

Yes. This is correct.

> > 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?

Yes, it would involve building the fedora docker base image from scratch. Now,
the process which currently generates that image (hopefully by running some
sort of tool or script to generate the image from pre-built Fedora RPMS) could
also generate an RPM with:
* a list of the Name-Version-Release data of the binary Fedora RPMS, and their
corresponding SRPMS, and instructions on where to find these items in Koji.
* a copy of the Fedora docker base image

The idea being that anyone who gets that Fedora docker base image via RPM will
also get a list of the source and binary Fedora RPMS used to compose it, and
can go get them from Koji or the repositories in order to comply with the
source licenses. (There is a minimal risk of us garbage collecting these builds
depending on when this is done...)

If we were trying to be very clever, we'd wrap all of the image creation logic
inside a SRPM with the proper BuildRequires, so that someone could simply
rpmbuild --rebuild that SRPM to generate a custom (updated/tweaked) Fedora
docker base image in an RPM. However, this aspect of it is not a legal
requirement, just a nice-to-have.

-- 
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





[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]