The Gentoo Arch Testing Tool (Gatt) is meant for all people in the Gentoo environment that need to handle keywording. Traditionally the package tree is in constant movement, where all supported architectures (this mostly covers processor types) are handled individually. Taking a package from the testing area to the stable branch is the task of people using "their" platform and verifying that a given package really works there and is ready to go stable. Or to mark packages as testing that had no support for the architecture before. All this is called keywording, originating from the KEYWORDS variable in the ebuild.
Selecting a package and then maybe needing to hassle with dependencies that are also in testing can be boring manual work. So individuals created scripts on their own to help them or use some other very special work-flow which they created over time. Gatt is now an easy way to handle all this including some special tasks that a template can do for the user, some advanced examples are shipped with it.
This also aims at novices in the architecture work of Gentoo, mainly the Arch Testers several teams have. Anyway, before handling all this you should have an idea about how stabilisations work in Gentoo land and understood Portage's masking and keyword mechanisms. This manual is no introduction to Portage.
If you find any errors in the program or the documentation please contact the main authors of either (email contact to be found in the AUTHORS file shipped with Gatt).
For a quick glance what it can do, Examples and have a look at the file TUTORIAL shipped with Gatt. For reference purposes read the corresponding sections on the available options. When working with templates, you need to know the basics described in Files before you thoroughly work through everything in Templates to understand the work-flow.
generated by
GNU texinfo 4.13
hosted on