「DeveloperWiki:パッケージのテスト」の版間の差分
(セクション見出しの訳出) |
|||
| 1行目: | 1行目: | ||
[[Category:DeveloperWiki]] |
[[Category:DeveloperWiki]] |
||
| + | [[en:DeveloperWiki:Package Testing]] |
||
| − | = Testing Overview = |
||
| + | = テスト概要 = |
||
The intended purpose of the testing repo is to provide a staging area for packages to be placed prior to acceptance into the main repositories. Package maintainers (and general users) can then access these testing packages to make sure that there are no problems integrating the new package. Once a package has been tested and no errors are found, the package can then be moved to the primary repositories. |
The intended purpose of the testing repo is to provide a staging area for packages to be placed prior to acceptance into the main repositories. Package maintainers (and general users) can then access these testing packages to make sure that there are no problems integrating the new package. Once a package has been tested and no errors are found, the package can then be moved to the primary repositories. |
||
| 8行目: | 9行目: | ||
Packages that can affect many packages (such as perl or python) should be tested as well. Testing can also be used for large collections of packages such as GNOME and KDE. |
Packages that can affect many packages (such as perl or python) should be tested as well. Testing can also be used for large collections of packages such as GNOME and KDE. |
||
| − | '''WARNING:''' Developers must [[DeveloperWiki: |
+ | '''WARNING:''' Developers must [[DeveloperWiki:クリーンな chroot 内でビルドする|build their packages in a clean chroot]] to avoid providing packages that have linking/run-time dependencies on packages from the [testing] repository. |
| − | For detailed instructions on moving a package between testing and the main repositories, see [[DeveloperWiki: |
+ | For detailed instructions on moving a package between testing and the main repositories, see [[DeveloperWiki:パッケージャになる方法]] |
2020年5月31日 (日) 11:34時点における版
テスト概要
The intended purpose of the testing repo is to provide a staging area for packages to be placed prior to acceptance into the main repositories. Package maintainers (and general users) can then access these testing packages to make sure that there are no problems integrating the new package. Once a package has been tested and no errors are found, the package can then be moved to the primary repositories.
Not all packages need to go through this testing process, however all packages destined for [core] MUST go to testing first.
Packages that can affect many packages (such as perl or python) should be tested as well. Testing can also be used for large collections of packages such as GNOME and KDE.
WARNING: Developers must build their packages in a clean chroot to avoid providing packages that have linking/run-time dependencies on packages from the [testing] repository.
For detailed instructions on moving a package between testing and the main repositories, see DeveloperWiki:パッケージャになる方法