 -New_PRoject(1)

NAME
-New_PRoject - create a new project

SYNOPSIS
-New_PRoject project-name [ option... ]
-New_PRoject -List [ option... ]
-New_PRoject -Help

DESCRIPTION
The -New_PRoject command is used to create a new project. The project is created as an empty directory structure with no staff except the administrator, no changes, and branches to implement the version specified.

Please note: unless you specify a version (see the -version option, below) this command will default to creating branches to support version 1.0. If you discovered this too late, all is not lost: you can use the aenbru(1) command to get rid of the branches you didn't want.

  Directory
The project directory, under which the project baseline and history and state and change data are kept, will be created at this time. If the -DIRectory option is not given, the project directory will be created in the directory specified by the default_project_directory field of aeuconf(5), or if not set in current user's home directory; in either case with the same name as the project.

  Staff
The project is created with the current user and group as the owning user and group. The current user is an administrator for the project. The project has no developers, reviewers, integrators or other administrators. The project's umask is derived from the current user's umask, but guaranteeing that group members will have access and that only the project owner will have write access.

  Pointer
The project pointer will be added to the first element of the search path, or if no path is set. If this is inappropriate, use the -LIBrary option to explicitly set the desired location. See the -LIBrary option for more information.

  Version
You may specify the project version in two ways:

1.  The version number may be implicit in the project name, in which case the version numbers will be stripped off. For example, ``aenpr example.1.2'' will create a project called ``example'' with branch number 1 created, and sub-branch 2 of branch 1 created.

2.  The version number may be stated explicitly, in which case it will be subdivided for branch numbers. For example, ``aenpr example -version 1.2'' will create a project called ``example'' with branch number 1 created, and sub-branch 2 of branch 1 created.

In each case, these branches may be named wherever a project name may be given, such as ``-p example.1'' and ``-p example-1.2''. The actual punctuation character is unimportant.

You may have any depth of version numbers you like. Both methods of specifying version numbers may be used, and they will be combined. If you want no version numbers at all, use -version with a single dash as the argument, as in ``-version -''

If no version number is given, either explicitly or implicitly, version 1.0 is used.

  Project Directory Location

OPTIONS
The following options are understood:

-Keep
    This option may be used to re-attach a project detached using aermpr -keep and possibly moved by the system administrator.

-VERSion number
    This option may be used to specify the version number for the project. Version numbers are implemented as branches. Use a single dash (``-'') as the argument if you want no version branches created.

RECOMMENDED ALIAS
The recommended alias for this command is
csh%	alias aenpr ' -npr \!* -v'
sh$	aenpr(){ -npr "$@" -v}

ERRORS
It is an error if the project name already exists.
It is an error if the project directory already exists.
It is an error if the current user does not have sufficient permissions to create the directory specified with the -DIRectory option.

SEE ALSO

aena(1)
    add a new administrator to a project

aenbru(1)
    Remove a new branch. This can often be useful if aenpr(1) created some default branches for you, and now you want to get rid of them.

aenc(1)
    add a new change to a project

aend(1)
    add a new developer to a project

aenrls(1)
    create a new project from an existing project

aenrv(1)
    add a new reviewer to a project

aermpr(1)
    remove project

aeuconf(5)
    user configuration file format