RPM Support

To publish a tree info you'll need to extend the existing publication to account for:

• The treeinfo file that is equivalent to the data stored in the DistributionTree content unit. This will become PublishedMetadata (see the plugin API).

• The additional subrepos (the ones with the repodata folders in them). You'll need to use createrepo_c interfaces to generate the metadata for those as well. This will be similar to existing codepaths that sync already uses to publish the main repo.

• In addition to the subrepo metadata (the repodata dir) you'll need to have the rpms themselves be available as PublishedArtifacts too.

• Single files that need to be available also need to be there. For example the "image" files. Those are saved as Artifacts at sync time (I think) and so to publish those you would create a PublishedArtifact for each.