-
Notifications
You must be signed in to change notification settings - Fork 42
Closed
Description
This is mainly with respect to official distro RPM updates:
Problem:
- The config files and docs in each of common, image, storage need to be shipped in the containers-common rpm.
- Upstream releases/tags are done per subproject.
- This can be a problem for updating the containers-common rpm via Packit because Packit reacts to github releases and only finding a subproject in each release will mean some config files can't be found.
- Triggering updates to containers-common rpm on releases of c/image and c/storage could also cause trouble.
Proposal:
- Move all files and docs inside the common/ subproject and set Packit to react to only
common-releases
OR - Use a single version for the entire container-libs project, publish the entire source on every release.
OR - Do some Packit gymnastics to handle rpms with the way things are now (I'd rather not). Consolidating the three into a monorepo would simplify COPR rpm builds by a lot and I'd rather be able to use that same simplification in official distro updates too.
Metadata
Metadata
Assignees
Labels
No labels