Go to the first, previous, next, last section, table of contents.
Either regular modules or ampersand modules can contain
options, which supply additional information concerning
the module.
-d name
-
Name the working directory something other than the
module name.
-e prog
-
Specify a program prog to run whenever files in a
module are exported. prog runs with a single
argument, the module name.
-i prog
-
Specify a program prog to run whenever files in a
module are committed. prog runs with a single
argument, the full pathname of the affected directory
in a source repository. The `commitinfo',
`loginfo', and `verifymsg' files provide other
ways to call a program on commit.
-o prog
-
Specify a program prog to run whenever files in a
module are checked out. prog runs with a single
argument, the module name.
-s status
-
Assign a status to the module. When the module file is
printed with `cvs checkout -s' the modules are
sorted according to primarily module status, and
secondarily according to the module name. This option
has no other meaning. You can use this option for
several things besides status: for instance, list the
person that is responsible for this module.
-t prog
-
Specify a program prog to run whenever files in a
module are tagged with
rtag
. prog runs
with two arguments: the module name and the symbolic
tag specified to rtag
. It is not run
when tag
is executed. Generally you will find
that taginfo is a better solution (see section User-defined logging).
-u prog
-
Specify a program prog to run whenever `cvs
update' is executed from the top-level directory of the
checked-out module. prog runs with a single
argument, the full path to the source repository for
this module.
You should also see see section How the modules file "program options" programs are run about how the
"program options" programs are run.
Go to the first, previous, next, last section, table of contents.