YAML File Compilation Guide
2020-08-11How to contributeProcess specifications
1. Introduction
The .yaml file contains the upstream community information of the software packages in the openEuler repository, facilitating unified verification and management.
2. Requirements of File Naming and Storage Path
The .yaml file name must be the same as the repository name and be in the same directory as that of the .spec file. Generally, the yaml file is stored in the root directory. For example, the name of the .yaml file in the oemaker code repository is oemaker.yaml and the file is stored in the root directory.

3. Fields in the YAML File
In the .yaml file, the version_control, src_repo, tag_prefix, and separator fields need to be manually set.
| Field | Description | Remarks |
|---|---|---|
| version_control | Version control protocol used by the upstream repository | Currently, svn, git, hg, github, gnome, metacpan, pypi, and gitee are supported. |
| src_repo | Actual address of the upstream repository | You can use version_control and src_repo to download the corresponding code. |
| tag_prefix | Version prefix in the tag of the upstream repository | For example, If the tag provided by the upstream is v1_0_1, tag_prefix must be set to ^v. |
| separator | Version separator in the tag | For example, if the tag provided by the upstream is v1_0_1, separator must be set to _. |
4. Examples of YAML Files
| Version Control Protocol | Example (Link) |
|---|---|
| svn | amanda.yaml |
| git | mdadm.yaml |
| hg | nginx.yaml |
| github | asciidoc.yaml |
| gnome | gnome-terminal.yaml |
| metacpan | perl-Authen-SASL.yaml |
| pypi | python-apipkg.yaml |
| gitee | oemaker.yaml |
[Copyright] Copyright © 2026 openEuler Community. This article is first released by the openEuler community. Please reproduce it in compliance with the CC-BY-SA 4.0 license. Please note the text and keep the original link and author information when reproducing the article.
[Disclaimer] This article only represents the author's opinions, and is irrelevant to this website. This website is neutral in terms of the statements and opinions in this article, and does not provide any express or implied warranty of accuracy, reliability, or completeness of the contents contained therein. This article is for readers' reference only, and all legal responsibilities arising therefrom are borne by the reader himself.