| Top | |
|
|
|
Modulemd.ModuleIndexMergerModulemd.ModuleIndexMerger — Class to aid in merging metadata from multiple repositories. |
ModuleIndexMerger is used to resolve merges between multiple repository metadata sources, possibly with varying priorities.
It is expected to be used as follows (python example) by tools such as yum:
1 2 3 4 5 6 7 |
merger = Modulemd.ModuleIndexMerger.new() merger.associate_index(fedora_repo_index, 0) merger.associate_index(updates_repo_index, 0) merger.associate_index(updates_testing_repo_index, 0) merged_index = merger.resolve() |
In the above code, merged_index will be a complete, merged view of the metadata from all of the added ModulemdModuleIndex instances.
When merging module streams, entries will be deduplicated based on whether they share the same module name, stream name, version number, and context. At present, libmodulemd does not interrogate more closely to determine if they have the same content, so if the repository configuration is broken and there exists two ModulemdModuleStream entries that have different content for the same NSVC, the behavior is undefined.
Merging ModulemdDefaults entries behaves as follows:
Within a ModuleIndex, if two or more default entries reference the same module, the one with the highest modified field will be used and the others discarded.
When merging ModuleIndexes, if two or more indexes contain Defaults for the same module, but different modified values, the one with the highest modified value will be used and the others discarded.
Any module default that is provided by a single repository is authoritative.
If the repos have different priorities (not common), then the default for this module and stream name coming from the repo of higher priority will be used and the default from the lower-priority repo will not be included even if it has a higher modified value.
If the repos have the same priority (such as "fedora" and "updates" in the Fedora Project) and modified value, the entries will be merged as follows:
If both repositories specify the same default stream for the module, use it.
If either repository specifies a default stream for the module and the other does not, use the one specified.
If both repositories specify different default streams, the merge will unset the default stream and proceed with the merge.
If both repositories specify a set of default profiles for a stream and the sets are equivalent, use that set.
If one repository specifies a set of default profiles for a stream and the other does not, use the one specified.
If both repositories specify a set of default profiles for a stream and each are providing a different set, this is an unresolvable merge conflict and the merge resolution will fail and report an error.
Intents behave in exactly the same manner as described for the top-level defaults, except that they merge beneath each intent name.
Merging ModulemdTranslations entries behaves as follows:
For each translated summary, description and profile description, compare
the modified value of the Translation document matching this module name
and stream. Whichever has the higher value will be used. Any translation
containing the empty string will be interpreted as removing the
translation. Subsequent processing of a higher modified value may restore
it.
ModulemdModuleIndexMerger *
modulemd_module_index_merger_new (void);
Since: 2.0
void modulemd_module_index_merger_associate_index (ModulemdModuleIndexMerger *self,ModulemdModuleIndex *index,gint32 priority);
Enqueues a ModulemdModuleIndex representing the parsed metadata from a repository into this ModulemdModuleIndexMerger for merging and deduplication of other repositories.
Once all repositories have been added, call
modulemd_module_index_merger_resolve() to perform the merge.
self |
This ModulemdModuleIndexMerger object. |
[in] |
index |
A ModuleIndex, usually constructed by reading
the module metadata from a repository with
|
[in][transfer none] |
priority |
The priority of the repository that the entries in |
[in] |
Since: 2.0
ModulemdModuleIndex * modulemd_module_index_merger_resolve (ModulemdModuleIndexMerger *self,GError **error);
Merges all added ModulemdModuleIndex objects according to their priority. The logic of this merge is described in the Description of ModulemdModuleIndexMerger.
Once this function has been called, the internal state of the
ModulemdModuleIndexMerger is undefined. The only valid action on it after
that point is g_object_unref().
self |
This ModulemdModuleIndexMerger object. |
[in] |
error |
A GError containing the reason for a failure to resolve the merges. |
[out] |
A newly-allocated ModulemdModuleIndex containing
the merged results. If this function encounters an unresolvable merge
conflict, it will return NULL and set error
appropriately.
Since: 2.0