> Bill Sommerfeld <sommerfeld at sun.com> writes: >>>> WES-3 Should we set CODEMGR_WS in the non-teamware case? >>> We've been back and forth a few times on the use of CODEMGR_WS, my >>> view (which I think was shared by stevel) is that CODEMGR_WS, while >>> originally used by and for teamware, has effectively become generic at >>> this point, and that picking different variables to hold the workspace >>> root merely because the SCMs differ would create yet another thing for >>> users and the tools to keep track of with little benefit. >> what I think would make sense would be to set a different, >> non-teamware-specific variable. So a teamware workspace would get >> CODEMGR_WS and the TBD additional variable; mercurial would just get the >> TBD additional variable. >
The advantage of having a new variable is we can start fresh with Hg. The disadvantage is, there are workspaces outside of Sun that talk about setting the CODEMGR_WS variable to get the code to compile outside of TW. So, some docs and Makefiles would be affected. Also, CODEMGR_WS seems general enough to be used with any SCM system if we ever decide to use something else in the distant future. So, I lean toward keeping it, but if we do decide to change it, we would have to evaluate the impact on code and documentation. Cheers, Jim
