From Fedora Project Wiki
(Created page with "{{ draft }} = Image Assembly Overview = The Env_Stacks/Projects/SoftwareComponentPipeline is designed to make it straightforward to automatically produce updated RPMs an...") |
No edit summary |
||
| Line 3: | Line 3: | ||
= Image Assembly Overview = | = Image Assembly Overview = | ||
The [[ | The [[Env_and_Stacks/Projects/SoftwareComponentPipeline]] is designed to make it straightforward to automatically produce updated RPMs and RPM repositories from upstream components releases. | ||
However: | However: | ||
Revision as of 12:50, 24 September 2015
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
It is still under construction and content may change. Do not rely on the information on this page.
Image Assembly Overview
The Env_and_Stacks/Projects/SoftwareComponentPipeline is designed to make it straightforward to automatically produce updated RPMs and RPM repositories from upstream components releases.
However:
- not all upstream applications (especially web applications) are amenable to being disassembled into component RPMs
- the high level "application glue code" that combines dependencies into a coherent application typically isn't designed for reuse
- packaging things as RPMs is very helpful for building Fedora itself, but markedly less so when building things to run *on* Fedora
These recommendations cover the available approaches to assembling individual components produced by the software component pipeline into larger binary images for easier consumption.