I've recently had a few conversations with folks that were wanting to
know "what about non-RPM packaging formats?" in relation to the
software component pipeline.
My answer to that is "use source-to-image to layer non-RPM components
atop lower level images assembled from RPMs", but that's not really
written down anywhere public.
Accordingly, while it likely isn't the right long term home, I started
a page for "Image Assembly Recommendations" at
The idea there is for us to start capturing more about how folks can
use the *output* of the software component pipeline, both standalone
and in combination with other non-RPM bits, to create larger binary
Most of those are still "built RPMs in -> binary artifact out", but
layered images are the one case that aren't necessarily purely about
assembly of already built components: source-to-image may be used to
bring in source dependencies using language specific tools (maven,
npm, bower, pip, gem, cpan, composer, etc), as well as application
source code directly from git repos.
While my initial write-up talks specifically about how each kind of
artifact is likely to be built in Fedora, it likely makes more sense
from an Envs & Stacks perspective to talk about them more generally in
a way that's also useful to Fedora remixes and derivatives, and then
point to Fedora's usage as an example.
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia