Next: , Previous: Templates, Up: Top


4 Files

4.1 gattrc

The file .gattrc in the home directory of the user calling gatt can hold often needed information so you don't have to give it on the command line every time. At the moment three settings can be set there:

template-script-dir=<arg>
location where gatt should look for script-templates
script-dest-dir=<arg>
location where generated scripts should be stored
post-resolve-script-from=<arg>
name of the template file (respects template-script-dir)

4.2 package.keywords

Gatt knows about the status of a package by adding information next to it in the file package.keywords, hidden as a comment so Portage is not bothered by the entries.

4.2.1 Initial emerge

When working on a bug for the first time, Gatt adds the following entry:

        ###### for bug 194959 {
        ## attribute: uninstall
        =sci-calculators/pcalc-1.1
        ###### }

Indicated are the number of the processed bug, the attribute depending on the state of the package when Gatt was first called and the package atom. The latter is not protected by comment signs, because the information is for Portage, too.

Possible attributes are

uninstall
Package has not been installed before and will be removed when cleaning out old entries
keep
Packages has been installed before and will be kept

4.2.2 Resolving a bug

When resolving a bug, the bug number is not kept anymore as the package has been processed entirely: Either a template (see Templates for details) has been used to step further in the work-flow, the package has been removed or is kept. This leads to a slightly changed entry, where all packages are grouped into one removal section when calling Gatt for more than one bug.

        ###### slated for removal {
        ## attribute: keep
        =net-fs/samba-3.0.27a
        ###### }

The attributes are the same as for entries on initial addition and are kept for reference.

4.2.3 Cleaning up

The clean action leads to a removal of entries from the package.keywords file, if this is possible without much hassle for the dependency tree generation of Portage.