2 Invoking Gatt
Gatt is called with an action to be performed, whose behaviour is
modified by options.
2.1 Actions
The possible actions are the following:
- -w, --work-on <bug number>
- prepare the system to work-on on a new bug
- -g --give-me <section name> <package atom>
- install unstable packages on stable systems filed under a freely
choosable section name
- -r, --resolve <bug number>
- remove all stuff connected to a given bug from the system
- -d, --drop <section name>
- drops the given free section from the package files
- -c, --clean <arg>
- Drop entries from keyword/use/unmask files that meet certain criteria
and possibly uninstall some of them. The following arguments are
recognized:
- invalid
- See --stat.
- unneeded
- See --stat.
- unapplied
- See --stat.
- not-wanted.
- See --stat.
- -u, --use-desc <USE flag>
- display information for USE flags
- --stat <arg>
- display some information about a topic by giving one out of the
following as <arg>.
- summary
- Give a summary about all entries in your package files that are currently
managed by gatt.
- slated
- Only slated entries, but more detailed than summary.
- <section name>
- Give information about a free section in package.keywords (result of
–give-me e.g.).
- <bug number>
- Display what is associated with the given bug number in package.keywords.
- invalid
- All entries that are neither related to an installed package nor an ebuild in
any repository.
- unneeded
- An entry is considered to be unneeded if it could be removed without doing
any harm. More exactly, an entry is unneeded if it is invalid, or
contained in a free section or slated, while it is either not installed, or
already stable. Note that an entry contained in a Gatt bug section is never
considered to be unneeded.
- unapplied
- An entry is considered to be unapplied if the associated package is
not installed. The major difference to unneeded is, that this also
applies to bug sections.
- outdated
- Outdated are entries for packages that are installed, but are no longer
contained in any ebuild repository.
- not-wanted
- Normally, all entries in your slated section will have the attribute "keep".
However, you can of course manually give some of these entries the attribute
"uninstall", and Gatt will later classify these entries as not-wanted.
- -h, --help
- display a help message
- --version
- display the version of gatt
2.2 Options
Gatt can be controlled by options that change the behaviour of the
actions requested. There are different categories where the options intervene.
2.2.1 Gatt itself
- -p, --pretend
- only prints what the program would do if called without this flag (not
implemented yet)
- -v, --verbose
- be verbose
- -q, --quiet
- minimalistic output
- -I, --no-user-interaction
- don't ask any questions (only use if you know what you are doing)
2.2.2 Package manager related
- -f, --fetchonly
- only fetch the sources – do not actually build the package
- --with-use <USE flags>
- installs packages with additional USE flags (not implemented yet)
- --with-cflags <CFLAGS>
- installs packages with user defined cflags (not implemented yet)
- --no-tests
- don't add "test" but "-test" to FEATURES when merging packages
- --no-merge
- prevents gatt from installing/uninstalling packages
- -N, --newuse
- force package install when USE flags for already installed dependencies
change.
2.2.3 Miscellaneous
- --script-from <file name>
- generates a script from a user supplied template; at the moment this
only works in connection with 'resolve'
Options that should be normally set in your ~/.gattrc but can be
overridden from the command-line:
- --template-script-dir <template base directory>
- location where gatt should look for script-templates
- --script-dest-dir <destination base directory>
- location where generated scripts should be stored