aegis -New_ReLeaSe(1) General Commands Manual aegis -New_ReLeaSe(1) NNAAMMEE aegis new release - create a new project from an old-style project. SSYYNNOOPPSSIISS aaeeggiiss --NNeeww__RReeLLeeaaSSee project-name [ _n_e_w_-_p_r_o_j_e_c_t_-_n_a_m_e ][ _o_p_t_i_o_n... ] aaeeggiiss --NNeeww__RReeLLeeaaSSee --LLiisstt [ _o_p_t_i_o_n... ] aaeeggiiss --NNeeww__RReeLLeeaaSSee --HHeellpp DDEESSCCRRIIPPTTIIOONN The _a_e_g_i_s _-_N_e_w___R_e_L_e_a_S_e command is used to create a new project from an existing project. _I_t _c_r_e_a_t_e_s _a _n_e_w _p_o_s_t_-_3_._0 _p_r_o_j_e_c_t _f_r_o_m _a_n _o_l_d _p_r_e_-_3_._0 _p_r_o_j_e_c_t_. PPlleeaassee NNoottee:: If your old-style project does not have a version number in the project name, you _m_u_s_t supply a new project name, otherwise you will get an error. (If you want to re-use the old project name, you need to rename the old project, and then use _a_e_n_r_l_s to create a new new-style project with the old name. See the HOWTO for how to change a project's name.) This command was essential before the introduction of branches into the Aegis model. It is more useful to create a new release of a project by ending development on the branch of the previous release and starting development of a new branch numbered for the desired release. Once you have a new-style project, use the _a_e_n_b_r(1) command to create new branches on this project. This provides more efficient release management, and allows historical versions to be reproduced more sim- ply. If no _n_e_w_-_p_r_o_j_e_c_t_-_n_a_m_e is specified, it will be derived from the project given as follows: any minor version dot suffix will be removed from the name, then any major version dot suffix will be removed from the name. A major version dot suffix will be appended, and then a minor version dot suffix will be appended. As an example, "foo.1.0" would become "foo.1.1" assuming the default minor version increment, and "foo" would become "foo.1.1" assuming the same minor version increment. The entire project baseline will be copied. The project state will be as if change 1 had already been integrated, naming every file (in the old project) as a new file. The history files will reflect this. No build will be necessary; it is assumed that the old baseline was built successfully. Change numbers will commence at 2, as will build num- bers. Test numbers will commence where the old project left off (because all the earlier test numbers were used by the old project). The default is for the minor version number to be incremented. If the major version number is incremented or set, the minor version number will be set to zero if it is not explicitly given. The pointer to the new project will be added to the first element of the search path, or _/_u_s_r_/_l_o_c_a_l_/_c_o_m_/_a_e_g_i_s if none is set. If this is inappropriate, use the --LLIIBBrraarryy option to explicitly set the desired location. See the --LLIIBBrraarryy option for more information. 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 --DDIIRReeccttoorryy option is not given, the project directory will be cre- ated in the directory specified by the default_project_directory field of the project user's _a_e_u_c_o_n_f(5), or if not set in project user's home directory; in either case with the same name as the project. All staff will be copied from the old project to the new project with- out change, as will all of the project attributes. TTHHEE BBAASSEELLIINNEE LLOOCCKK The baseline lock is used to ensure that the baseline remains in a consistent state for the duration of commands which need to read the contents of files in the baseline. The commands which require the baseline to be consistent (these include the _a_e_b(1), _a_e_c_p(1) and _a_e_d(1) commands) take a baseline _r_e_a_d lock. This is a non-exclusive lock, so the concurrent development of changes is not hindered. The command which modifies the baseline, _a_e_i_p_a_s_s(1), takes a baseline _w_r_i_t_e lock. This is an exclusive lock, forcing _a_e_i_p_a_s_s(1) to block until there are no active baseline read locks. It is possible that one of the above development commands will block until an in-progress _a_e_g_i_s _-_I_n_t_e_g_r_a_t_e___P_A_S_S completes. This is usually of short duration while the project history is updated. The delay is essential so that these commands receive a consistent view of the baseline. No other integration command will cause the above develop- ment commands to block. When aegis' branch functionality is in use, a read (non-exclusive) lock is taken on the branch baseline and also each of the "parent" baselines. However, a baseline write (exclusive) lock is only taken on the branch baseline; the "parent" baselines are only read (non- exclusive) locked. PPrroojjeecctt DDiirreeccttoorryy LLooccaattiioonn PPlleeaassee NNoottee:: Aegis also consults the underlying file system, to deter- mine its notion of maximum file size. Where the file system's maximum file size is less than _m_a_x_i_m_u_m___f_i_l_e_n_a_m_e___l_e_n_g_t_h, the filesystem wins. This can happen, for example, when you are using the Linux UMSDOS file system, or when you have an NFS mounted an ancient V7 filesystem. Setting _m_a_x_i_m_u_m___f_i_l_e_n_a_m_e___l_e_n_g_t_h to 255 in these cases does not alter the fact that the underlying file systems limits are far smaller (12 and 14, respectively). If your development directories (or your whole project) is on filesys- tems with filename limitations, or a portion of the heterogeneous builds take place in such an environment, it helps to tell Aegis what they are (using the project _c_o_n_f_i_g file's fields) so that you don't run into the situation where the project builds on the more permissive environments, but fails with mysterious errors in the more limited environments. If your development directories are routinely on a Linux UMSDOS filesystem, you would probably be better off setting _d_o_s___f_i_l_e_- _n_a_m_e___r_e_q_u_i_r_e_d _= _t_r_u_e, and also changing the _d_e_v_e_l_o_p_m_e_n_t___d_i_r_e_c_t_o_r_y___t_e_m_- _p_l_a_t_e field. Heterogeneous development with various Windows environ- ments may also require this. OOPPTTIIOONNSS The following options are understood: --DDIIRReeccttoorryy _p_a_t_h This option may be used to specify which directory is to be used. It is an error if the current user does not have appro- priate permissions to create the directory path given. This must be an absolute path. Caution: If you are using an automounter do not use `pwd` to make an absolute path, it usually gives the wrong answer. --HHeellpp This option may be used to obtain more information about how to use the _a_e_g_i_s program. --LLIIBBrraarryy _a_b_s_p_a_t_h This option may be used to specify a directory to be searched for global state files and user state files. (See _a_e_g_s_t_a_t_e(5) and _a_e_u_s_t_a_t_e(5) for more information.) Several library options may be present on the command line, and are search in the order given. Appended to this explicit search path are the directories specified by the _A_E_G_I_S___P_A_T_H environment vari- able (colon separated), and finally, _/_u_s_r_/_l_o_c_a_l_/_l_i_b_/_a_e_g_i_s is always searched. All paths specified, either on the command line or in the _A_E_G_I_S___P_A_T_H environment variable, must be abso- lute. --LLiisstt This option may be used to obtain a list of suitable subjects for this command. The list may be more general than expected. --NNoott__LLooggggiinngg This option may be used to disable the automatic logging of output and errors to a file. This is often useful when sev- eral aegis commands are combined in a shell script. --TTEERRssee This option may be used to cause listings to produce the bare minimum of information. It is usually useful for shell scripts. --VVeerrbboossee This option may be used to cause aegis to produce more output. By default aegis only produces output on errors. When used with the --LLiisstt option this option causes column headings to be added. --VVEERRSSiioonn _n_u_m_b_e_r This option may be used to specify the version number for the project. Version number are implemented as branches. Use the empty string as the argument if you want no version branches created. --WWaaiitt This option may be used to require Aegis commands to wait for access locks, if they cannot be obtained immediately. Defaults to the user's _l_o_c_k___w_a_i_t___p_r_e_f_e_r_e_n_c_e if not specified, see _a_e_u_c_o_n_f(5) for more information. --NNoo__WWaaiitt This option may be used to require Aegis commands to emit a fatal error if access locks cannot be obtained immediately. Defaults to the user's _l_o_c_k___w_a_i_t___p_r_e_f_e_r_e_n_c_e if not specified, see _a_e_u_c_o_n_f(5) for more information. See also _a_e_g_i_s(1) for options common to all aegis commands. All options may be abbreviated; the abbreviation is documented as the upper case letters, all lower case letters and underscores (_) are optional. You must use consecutive sequences of optional letters. All options are case insensitive, you may type them in upper case or lower case or a combination of both, case is not important. For example: the arguments "-project", "-PROJ" and "-p" are all inter- preted to mean the --PPrroojjeecctt option. The argument "-prj" will not be understood, because consecutive optional characters were not supplied. Options and other command line arguments may be mixed arbitrarily on the command line, after the function selectors. The GNU long option names are understood. Since all option names for _a_e_g_i_s are long, this means ignoring the extra leading '-'. The "----_o_p_t_i_o_n==_v_a_l_u_e" convention is also understood. RREECCOOMMMMEENNDDEEDD AALLIIAASS The recommended alias for this command is csh% alias aenrls 'aegis -nrls \!* -v' sh$ aenrls(){aegis -nrls "$@" -v} EERRRROORRSS It is an error if the old project named does not exist. It is an error if the old project named has not yet had any changes integrated. It is an error if the old project named has any changes not in the _c_o_m_p_l_e_t_e_d state. It is an error if the current user is not an administrator of the old project. EEXXIITT SSTTAATTUUSS The _a_e_g_i_s command will exit with a status of 1 on any error. The _a_e_g_i_s command will only exit with a status of 0 if there are no errors. EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS See _a_e_g_i_s(1) for a list of environment variables which may affect this command. See _a_e_p_c_o_n_f(5) for the project configuration file's _p_r_o_j_e_c_t___s_p_e_c_i_f_i_c field for how to set environment variables for all commands executed by Aegis. SSEEEE AALLSSOO _a_e_n_p_r(1) create a new project _a_e_r_m_p_r(1) remove project _a_e_u_c_o_n_f(5) user configuration file format CCOOPPYYRRIIGGHHTT aegis version 4.25.D611 Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Peter Miller The aegis program comes with ABSOLUTELY NO WARRANTY; for details use the '_a_e_g_i_s _-_V_E_R_S_i_o_n _L_i_c_e_n_s_e' command. This is free software and you are welcome to redistribute it under certain conditions; for details use the '_a_e_g_i_s _-_V_E_R_S_i_o_n _L_i_c_e_n_s_e' command. AAUUTTHHOORR Peter Miller E-Mail: pmiller@opensource.org.au /\/\* WWW: http://miller.emu.id.au/pmiller/ _A_e_g_i_s _U_s_e_r _G_u_i_d_e The chapter on _B_r_a_n_c_h_i_n_g has useful information about releases and branching. Reference Manual Aegis aegis -New_ReLeaSe(1)