Difference between revisions of "DeveloperWiki:Package Testing"

From ArchWiki
Jump to: navigation, search
m
(simplification of wikilinks, fixing whitespace (https://github.com/lahwaacz/wiki-scripts/blob/master/link-checker.py))
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:DeveloperWiki]]
 +
{{Merge|Official repositories|Merge to testing section.}}
 
= Testing Overview =
 
= Testing Overview =
  
Line 7: Line 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:Building in a Clean Chroot | build their packages in a clean chroot]] to avoid providing packages that have linking/run-time dependencies on packages from the [testing] repository.
+
'''WARNING:''' Developers must [[DeveloperWiki:Building in a Clean 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:HOWTO Be A Packager]]
 
For detailed instructions on moving a package between testing and the main repositories, see [[DeveloperWiki:HOWTO Be A Packager]]

Latest revision as of 09:51, 31 May 2015

Merge-arrows-2.pngThis article or section is a candidate for merging with Official repositories.Merge-arrows-2.png

Notes: Merge to testing section. (Discuss in Talk: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.

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:HOWTO Be A Packager