Table of Contents
This page is a quick reference into the common Aegis commands.
command_name” can be used to get
on a particular command.
See also the official Aegis quick reference in the User Guide.
-p name” option is used to specify the project name.
-c number” option is used to specify the
-l” (or “
-List”) option can often
be used to
list subjects for the given command (eg. change numbers or projects) or
simply to list rather than edit (e.g. a file or change attributes).
Set current project number for all following Aegis commands. The ae_p command with no arguments will `unset' this forced default.
Set current change number for all following Aegis commands. The ae_c command with no arguments will `unset' this forced default.
Change directory [change to baseline].
Aegis build - used by developers, reviewers and/ or integrators.
Run tests - used by developers.
Difference of change files with baseline.
View difference files generated with aed.
List change details.
Edit [list] change attributes.
Create a new change (see aenc(1) for details), using a GUI interface. This makes it a damn sight easier to type in the description field.
Edit change attributes (see aeca(1) for details), using a GUI interface. This makes it a damn sight easier to edit the description field.
List all of the lists (there are a lot).
List all of the changes for a project (branch).
List all of the files in a change.
This is a man page documenting the
~/.aegisrc file format.
Procedure: ael cd → aedb → do stuff → aeb → aet → aed → aedless [ → aeclean ] → aede
Develop begin [undo].
Develop end [undo].
This will remove all files in the development directory which are not in the change as new files or copied files. This may delete files that you want, so be careful.
The aeclean(1) command uses Aegis' knowledge of what is supposed to be in the change. You are meant to tell Aegis about all source files you create in a development directory. If you have forgotten to do this, it is highly likely that the integration would fail in any case.
If you are importing files from elsewhere, use “aenf .” and all of the files in the directory tree below dot (the current directory) will be added to the change (make sure there are no object files when you do this).
Prepares a file in the project for editing within the change; i.e. copy file into change from baseline. Remove symlink if necessary, etc.
Reverse the effects of the above.
Will check all files in your change to see if any have not been modified, and perform an aecpu on them. This will stop an unnecessary version number increment for files that have not changed. (And also improves test correlations.)
Merge out-of-date files.
-Only-merge option of the aed(1) command.
Create/ add a new file [undo].
Rename (move) files.
This tells Aegis the file is to be removed from the baseline when the change is integrated. Or aermu to undo this before the change is finished.
Procedure: ael cd → aecd → aedless → view output, review source files -> aerpass
Remember: the point of reviews is to find problems, not be a rubber stamp. You are expected to fail some reviews.
Review pass undo.
Procedure: aeib → aeb → aet → aed → aeipass
There is an aeintegratq(1) script distributed with Aegis to do this procedure automatically.
Integrate begin [undo].
This includes all of the commands that don't fit the categories above.
New developer; remove developer.
New reviewer; remover reviewer.
New integrator; remove integrator.
New (project) administrator; remove administrator.
Edit [list] project attributes (see
aepattr(5) for file format).
Edit [list] change attributes (see
aecattr(5) for file format).
Edit change attributes using a GUI. This makes it much easier to type in the description field.