Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

Subsections

• Synopsis
• Description
• Options
• Notes
• Diagnostics
• Examples
• Bugs
• See also
• Author

ac

Add an entry to an AIPS++ changelog file.

Synopsis

ac [

options for

ac]

Description

ac adds an entry to an AIPS++ changelog file.

ac assumes that you are working within a private directory tree which shadows that of the AIPS++ master source code tree, see mktree (p). It determines the appropriate changelog file from the current working directory.

ac invokes ao (p) to check out the appropriate changelog file. It also checks out another file which is used to generate a unique id for each change. Thereafter a glish script is started to let the user fill in a form for the change and to add the change to the changelog file. The user has the opportunity to abort the operation, in which case the checked out files are unlocked. In the change is added, ai (p) is invoked to check in the changed files.

Options

-i

Do only a check in of the changed files. This should only be used if the normal (automatic) check in failed because an exhale (p) has started or due to another error.

Notes

• The AIPS++ changelog files are meant to generate an overview (by buildchangelog (p)) of the new and changed features in an AIPS++ release. It means they are higher level than the RCS changelogs which are programmer oriented.

• Almost every source directory has a changelog file to keep track of the changes in the AIPS++ system.
  All glish subdirectories share a single changelog file in their root directory. The same is true for the system and the documentation subdirectories.

• The DISPLAY variable needs to be set, because ac uses a GUI to let the user fill in the change form.

• If checking out fails because the file does not exist yet, one should create an empty file changelog and check it in using ai (p). In general this should only occur in new directories.

• Checking in should normally succeed, but might fail because the an exhale (p) has started or because network connection is down. In that case ac should be run at a later time with the -i flag (to only do a checkin of the files).

Diagnostics

Status return values
0: success
1: initialization error
2: checkout failure
3: checkin failure
4: no change entry created by user

Examples

The command

   cd ~/aips++/code/aips/implement/Tables
   ac

will let the user fill in the change form and add the completed form to the changelog file of library module Tables.

Bugs

• ac does not detect why a checkout or checkin fails.

See also

rac (p) AIPS++ ac for remote users.
ai (p) AIPS++ code checkin utility.
ao (p) AIPS++ code checkout utility.
buildchangelog (p) process AIPS++ changelog files.

Author

Original: 2000/06/05 by Ger van Diepen, NFRA