Do we have some guidelines how to publish corresponding source code for container images?
I suppose that if the container image repository supports image layering, it should be possible to publish a layer on top, with the SRPMs for the RPMs used to construct the container image in the file system, and put that image in roughly the same place (where users hopefully can find it).
Thanks, Florian
On Thu, Apr 06, 2017 at 04:12:45PM +0200, Florian Weimer wrote:
Do we have some guidelines how to publish corresponding source code for container images?
I suppose that if the container image repository supports image layering, it should be possible to publish a layer on top, with the SRPMs for the RPMs used to construct the container image in the file system, and put that image in roughly the same place (where users hopefully can find it).
Is there any value in bundling them up in that way, rather than just pointing to the original source RPMs?
On 04/06/2017 06:32 PM, Matthew Miller wrote:
On Thu, Apr 06, 2017 at 04:12:45PM +0200, Florian Weimer wrote:
Do we have some guidelines how to publish corresponding source code for container images?
I suppose that if the container image repository supports image layering, it should be possible to publish a layer on top, with the SRPMs for the RPMs used to construct the container image in the file system, and put that image in roughly the same place (where users hopefully can find it).
Is there any value in bundling them up in that way, rather than just pointing to the original source RPMs?
We don't have stable locations for most source RPMs. The image could stay around beyond a Koji garbage collection run.
It's also my experience that those who do not ship sources with binaries automatically, as part of the same process, rarely deliver matching source code at all.
Thanks, Florian
-
Florian Weimer -
Matthew Miller