Version 1.9 Build 1556

News	FAQ
Search	Home

Next: buildchangelog Up: Code management Previous: avers

Subsections

`ax`

AIPS++ deletion utility.

Synopsis

ax [ -src | -sys | -top ] target1 [target2 ...] [...]

ax is used to delete AIPS++ files and directories. It does not delete them itself but instead appends deletion commands to the action list contained within ax_master (see below). It then invokes ax_master on the master AIPS++ RCS repository which must be available (see §1.1.4). The deletions will be applied to the slave RCS repositories and system by inhale (p) and sneeze (p) respectively. This mechanism allows AIPS++ slave sites to follow changes made to the master. General users can delete directories at or below the third level below $AIPSCODE (see §1.1.1). In particular, this includes module and application subdirectories. Deletion of higher-level directories is only allowed for members of the aips2mgr group.

ax_master does not actually delete anything from the AIPS++ master RCS repositories but instead ``rescinds'' them by renaming them so as to hide them from the code distribution system, see exhale (p). Rescinded files and directories are given names of the form .MM.NNN.filename, where MM.NNN is the AIPS++ version number at the time the file is rescinded (see avers (p)).

Options

-src

Delete a pair of files from the AIPS++ RCS repository and code subtree. The target must be specified as a pathname relative to $AIPSCODE (and therefore $AIPSLAVE and $AIPSMSTR, and need not have an RCS ,v suffix. For example,

   ax -src aips/apps/App1/App1.cc

would cause the following files to be deleted

   $AIPSMSTR/aips/apps/App1/App1.cc,v
   $AIPSLAVE/aips/apps/App1/App1.cc,v
   $AIPSCODE/aips/apps/App1/App1.cc

the first is rescinded when ax_master is invoked by ax itself, and the other two are deleted when ax_master is invoked by inhale (p). Note, however, that any executables associated with an application will not be deleted. These may be deleted explicitly by using the -sys option (see below).

If the target specified is a class implementation file, the object module will be deleted from the relevant library when ax_master is invoked by sneeze (p). For example,

   ax -src aips/implement/Class.cc

would result in the following deletions

   $AIPSMSTR/aips/implement/Class.cc,v
   $AIPSLAVE/aips/implement/Class.cc,v
   $AIPSCODE/aips/implement/Class.cc
   $AIPSARCH/lib/libaips.a(Class.o)
   $AIPSARCH/libdbg/libaips.a(Class.o)

If necessary, ax_master will also ranlib the object libraries and rebuild any sharable objects.

Directories specified as targets will be rescinded from the master and recursively deleted from the slave and code areas.

-sys

Delete a file from the AIPS++ system area. The target must be specified as a pathname relative to $AIPSARCH - the master, slave, and code areas are not affected. For example,

   ax -sys bin/Application bindbg/Application

would mark

   $AIPSARCH/bin/Application

and

   $AIPSARCH/bindbg/Application

for deletion by ax_master when invoked by sneeze (p).

Targets specified in the form x(y) denote library modules. For example,

   ax -sys lib/libaips.a(Class.o)

would mark Class.o for deletion from

   $AIPSARCH/lib/libaips.a

and

   $AIPSARCH/libdbg/libaips.a

by ax_master when invoked by sneeze (p). If necessary, ax_master would then ranlib the object libraries and rebuild any sharable objects.

A directory may be specified as the target, in which case it will be recursively deleted.

-top

Delete a file beneath $AIPSROOT. The target must be specified as a pathname relative to $AIPSROOT. This is a catch-all target and should only be used when the -src and -sys options are inappropriate.

If the target refers to a file in the master repository then it will be rescinded when ax_master is invoked by ax. If it refers to a file in the slave or code areas then it will be deleted when ax_master is invoked by inhale (p). If it refers to a file in the system area then it will be deleted when ax_master is invoked by sneeze (p) running on a machine of the corresponding architecture.

For example,

   ax -top docs/reference/Example.ps

would mark

   $AIPSROOT/docs/reference/Example.ps

for deletion by ax_master when invoked by inhale (p). Note the following:

   ax -top master/aips/apps/App1/App1.cc,v
   ax -top slave/aips/apps/App1/App1.cc,v
   ax -top rcs/aips/apps/App1/App1.cc,v

The first rescinds the master RCS version file, the second deletes the slave RCS version file, and by convention the third does both. Note that the RCS ,v suffix does need to be specified here.

A directory may be specified as the target, in which case it will be rescinded from the master and recursively deleted from the slave and code areas.

Resources

account.manager: Account name and group of the owner of the AIPS++ source code. ax only allows members of the aips2mgr group to delete higher-level directories. $HOME/.aipsrc is ignored.

Notes

Manual invokation of ax_master is forbidden. However, it may be of interest to know that it has a mode which causes it to apply all entries in its action list for the current major AIPS++ version. This is used by inhale (p) and sneeze (p) immediately before downloading a cumulative update.
When ax_master is invoked on the master RCS repositories it uses a temporary action list placed in $MSTRETCD/ax_list by ax. This mechanism prevents the same file from being rescinded twice from the master by ax_master in the same version of AIPS++.
ax may be disabled by creating a file $MSTRETCD/ax_disable. If this file contains any text it will be printed as an informative message to anyone trying to use ax.
ax must be owned by aips2mgr and have the setuid bit set.

Diagnostics

Status return values
0: success
1: initialization error
2: failed to get ax_master
3: argument error

Examples

To recursively delete module subdirectory trial/implement/Junk use

   ax -src trial/implement/Junk

Where several files are to be deleted, it may be convenient in csh and some other shells which allow it to use a command of the form

   cd /aips++/code
   ax -src aips/implement/\{Foo,Man,Chu}.*

Assuming the files existed, the shell would expand the argument to

   aips/implement/Foo.cc aips/implement/Foo.h \
   aips/implement/Man.cc aips/implement/Man.h \
   aips/implement/Chu.cc aips/implement/Chu.h \

Note that the 'cd /aips++/code' provided the context for the shell's wildcarding mechanism.

Refer also to the examples provided in the ``Options'' section above.

Bugs

ax requires that the host operating system support setuid shell scripts. Some operating systems, most notably Linux and Digital UNIX, do not support setuid shell scripts for security reasons.

Author

Original: 1992/05/14 by Mark Calabretta, ATNF.

Next: buildchangelog Up: Code management Previous: avers Contents Index