aedir(5) aedir(5) NNAAMMEE aedir - aegis directory structures DDEESSCCRRIIPPTTIIOONN The project directory structure is dictated by _a_e_g_i_s at the top level, but is completely under the project's control from various points below the top level. The project directory has the following contents _p_r_o_j_e_c_t/ baseline/ config _._._._p_r_o_j_e_c_t _s_p_e_c_i_f_i_c_._._. test/ _[_0_-_9_]_[_0_-_9_]/ t_[_0_-_9_]_[_0_-_9_]_[_0_-_9_]_[_0_-_9_]a.sh t_[_0_-_9_]_[_0_-_9_]_[_0_-_9_]_[_0_-_9_]m.sh history/ _._._._e_c_h_o _o_f _b_a_s_e_l_i_n_e_._._. delta._[_0_-_9_]_[_0_-_9_]_[_0_-_9_]/ _._._._e_c_h_o _o_f _b_a_s_e_l_i_n_e_._._. info/ state change/ _[_0_-_9_]/ _[_0_-_9_]_[_0_-_9_]_[_0_-_9_] The directory is structured in this way so that it is possible to pick an entire project up off the disk, and be confident that you got it all. The location of the root of this tree is configurable, and may even be changed during the life of a project. The contents of the _b_a_s_e_l_i_n_e subdirectory, other than those given, are defined by the project, and not dictated by aegis. The contents of the _d_e_l_t_a_._N_N_N directory, when it exists, are an image of the _b_a_s_e_l_i_n_e directory. It is frequently linked with the baseline, rather than a copy of it; see the _l_i_n_k___i_n_t_e_g_r_a_t_i_o_n___d_i_r_e_c_t_o_r_y field description in _a_e_p_c_o_n_f(5) for more information. The contents of the _h_i_s_t_o_r_y contains the edit histories of the _b_a_s_e_l_i_n_e directory, and is in all other ways an image of it. Note that _b_a_s_e_l_i_n_e always contains the latest source; the _h_i_s_t_o_r_y directory is just history. The actual files in the history directory tree will not always have names the same as those in the baseline; compare the methods used by SCCS and RCS. The contents of the _b_a_s_e_l_i_n_e_/_t_e_s_t directory are the tests which are created by changes. Test histories are also stored in the _h_i_s_t_o_r_y subdirectory. Tests are treated as project source. The edit histories are separated out to simplify the task of taking a "snapshot" of the source of a project, without airing all the dirty laundry. The _b_a_s_e_l_i_n_e directory always contains the latest source, and so the _h_i_s_t_o_r_y directory need not be readily accessible, because the build mechanism (something like _m_a_k_e(1), but preferably better) does not need to know anything about it. Similarly for tests. The _b_a_s_e_l_i_n_e_/_c_o_n_f_i_g file is used to tell aegis everything else it needs to know about a project. See _a_e_p_c_o_n_f(5) for more information. This file is a source file of the project, and is treated in the same way as all source files. SSEEEE AALLSSOO _a_e_n_c(1) create a new change _a_e_n_p_r(1) create a new project _a_e_g_i_s(5) aegis file format syntax _a_e_p_c_o_n_f(5) project configuration file format CCOOPPYYRRIIGGHHTT aegis version .C001 Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001 Peter Miller; All rights reserved. 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: millerp@canb.auug.org.au /\/\* WWW: http://www.canb.auug.org.au/~millerp/ Reference Manual Aegis 1