aegis -Make_Transparent(1) aegis -Make_Transparent(1) NNAAMMEE aegis make transparent - make branch file transparent SSYYNNOOPPSSIISS aaeeggiiss --MMaakkee__TTrraannssppaarreenntt [ _o_p_t_i_o_n... ] _f_i_l_e_n_a_m_e... aaeeggiiss --LLiisstt [ _o_p_t_i_o_n... ] aaeeggiiss --HHeellpp aaeeggiiss --VVEERRSSiioonn DDEESSCCRRIIPPTTIIOONN The _a_e_g_i_s _-_M_a_k_e___T_r_a_n_s_p_a_r_e_n_t command is used to add a file to the change which will result in the named file being made transparent in the branch when the change is integrated. The version of the project file from the deeper branch will then show through. You may name a directory to make all files in that directory tree transparent. It is an error if there are no relevant files. BBrraanncchh _v_s CChhaannggee The _a_e_c_p_u(1) command may only be applied to a change. If you wish to perform the same operation on a branch, use the _a_e_m_t(1) command, through the agency of a change. FFiillee NNaammee IInntteerrpprreettaattiioonn The aegis program will attempt to determine the project file names from the file names given on the command line. All file names are stored within aegis projects as relative to the root of the baseline directory tree. The development directory and the integration direc- tory are shadows of this baseline directory, and so these relative names apply here, too. Files named on the command line are first con- verted to absolute paths if necessary. They are then compared with the baseline path, the development directory path, and the integration directory path, to determine a baseline-relative name. It is an error if the file named is outside one of these directory trees. The --BBAAssee__RREEllaattiivvee option may be used to cause relative filenames to be interpreted as relative to the baseline path; absolute filenames will still be compared with the various paths in order to determine a baseline-relative name. The _r_e_l_a_t_i_v_e___f_i_l_e_n_a_m_e___p_r_e_f_e_r_e_n_c_e in the user configuration file may be used to modify this default behavior. See _a_e_u_c_o_n_f(5) for more infor- mation. PPrroocceessss SSiiddee EEffffeeccttss This command will cancel any build or test registrations, because changing the change file list logically invalidates them. NNoottiiffiiccaattiioonn The _m_a_k_e___t_r_a_n_s_p_a_r_e_n_t___c_o_m_m_a_n_d in the project configuration file is run, if set. The _p_r_o_j_e_c_t___f_i_l_e___c_o_m_m_a_n_d is also run, if set, and if there has been an integration recently. See _a_e_p_c_o_n_f(5) for more informa- tion. OOPPTTIIOONNSS The following options are understood: --BBAAssee__RREEllaattiivvee This option may be used to cause relative filenames to be con- sidered relative to the base of the source tree. See _a_e_u_- _c_o_n_f(5) for the corresponding user preference. --CCUUrrrreenntt__RREEllaattiivvee This option may be used to cause relative filenames to be con- sidered relative to the current directory. This is usually the default. See _a_e_u_c_o_n_f(5) for the corresponding user pref- erence. --CChhaannggee _n_u_m_b_e_r This option may be used to specify a particular change within a project. See _a_e_g_i_s(1) for a complete description of this option. --HHeellpp This option may be used to obtain more information about how to use the _a_e_g_i_s program. --LLiisstt This option may be used to obtain a list of suitable subjects for this command. The list may be more general than expected. --PPrroojjeecctt _n_a_m_e This option may be used to select the project of interest. When no --PPrroojjeecctt option is specified, the _A_E_G_I_S___P_R_O_J_E_C_T envi- ronment variable is consulted. If that does not exist, the user's _$_H_O_M_E_/_._a_e_g_i_s_r_c file is examined for a default project field (see _a_e_u_c_o_n_f(5) for more information). If that does not exist, when the user is only working on changes within a sin- gle project, the project name defaults to that project. Oth- erwise, it is an error. --TTEERRssee This option may be used to cause listings to produce the bare minimum of information. It is usually useful for shell scripts. --UUNNCChhaannggeedd Examine the named files to see if they are unchanged. Only remove the unchanged files from the branch, and leave the files which have changed. If no files are named on the com- mand line all branch files are checked. --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. --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 aemt 'aegis -mt \!* -v' sh$ aemt(){aegis -mt "$@" -v} This command is dedicated to my wife, Mary-Therese. When I was trying to explain what this command did, she said "I had one of those on my bicycle when I was young, but it fell off". EERRRROORRSS It is an error if the change is not in the _b_e_i_n_g _d_e_v_e_l_o_p_e_d state. It is an error if the change is not assigned to the current user. It is an error if the file is not present in the immediate branch. It is an error if the file is present in the immediate branch, but is not also present in a deeper branch. It is an error if the file is only present in the trunk branch. 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_c_p_u(1) uncopy copy files from a change _a_e_m_t_u(1) cease making branch files transparent 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/ Reference Manual Aegis aegis -Make_Transparent(1)