Acro source code was previously maintained in a CVS repository. The following information is maintained for historical reference.
software.sandia.gov:/space/CVS-Acro. The -d cvs option can be used to specify this directory for Acro CVS commands. For example, the following commandline checks out Acro:
cvs -d :ext:where@software.sandia.gov:/space/CVS-Acro checkout acro
<user-name> is your account name on software.sandia.gov. As an alternative, you can set the CVSROOT environmental variable in your unix shell instead of using the -d option.ssh when connecting to the repository. To do this, set the CVS_RSH environmental variable as follows:
CVS_RSH=sshNOTE: the cvs.a and ssh.cvs scripts can be used to setup these parameters. For example, the earlier command is simplified to
cvs.a checkout acro
cvs.a checkout acroUpdating edits commited by other developers:
cvs.a updateChecking for differences between your edits and what you initially checked out:
cvs.a diff
acro, which includes all of the Acro
projects that are available for general (unlimited) release. Per-project
Acro modules are also defined and can be checked out as
cvs.a checkout acro-<package>where <package> is one of the currently available projects described on the Acro project web pages. Note that the package name in the CVS checkout command should be lower case. For example, the command
cvs.a checkout acro-utilibchecks out the Acro UTILIB project only.
Note that the acro-<package> modules have acro as the top-level directory, and individual software packages are located in acro/packges. Some Acro projects are available as stand-alone libraries: APPSPACK, OPT++ and UTILIB. Thus, the command
cvs.a checkout utilibonly checks out the UTILIB software library, so the top-level directory is
utilib.