Mike Kupfer <mike.kupfer at sun.com> writes: >>>>>> "JimW" == Jim Walker <James.Walker at sun.com> writes: > > Bill> what I think would make sense would be to set a different, > Bill> non-teamware-specific variable. So a teamware workspace would get > Bill> CODEMGR_WS and the TBD additional variable; mercurial would just get > Bill> the TBD additional variable. > > JimW> The advantage of having a new variable is we can start fresh with > JimW> Hg. > > JimW> The disadvantage is, there are workspaces outside of Sun that talk > JimW> about setting the CODEMGR_WS variable to get the code to compile > JimW> outside of TW. So, some docs and Makefiles would be affected. > > JimW> Also, CODEMGR_WS seems general enough to be used with any SCM > JimW> system if we ever decide to use something else in the distant > JimW> future. > > JimW> So, I lean toward keeping it, but if we do decide to change it, we > JimW> would have to evaluate the impact on code and documentation. > > I agree that it would be cleaner to use a different name. I don't > agree that CODEMGR_WS is a general name per se, but maybe that's because > I remember when Teamware was called CodeManager. And if we're going to > use a different name, now would be a good time to introduce it. > > OTOH, I think that changing the variable name would introduce a lot of > churn--in our code, possibly code belonging to other groups, and in > documentation. And we do have a lot of other issues that I think are > more pressing. > > So I think we should stick with CODEMGR_mumble, though I reserve the > right to change my mind after sleeping on it. ;-)
Relay this bit from IRC. I agree with Mike that the churn is my primary concern (that's a large part of what I meant about it becoming generic, nearly everyone outside has never used Teamware/Codemgr, but have the CODEMGR_WS == my workspace connection firmly engrained, I would expect). However, I'd like to be sure that setting them doesn't induce breakage, confusion, or other call-generating things for anyone ws'd into an hg workspace and attempting to use teamware on something else, for whatever reason. If it's mild, or obvious, I may not mind. But if it's going to cause trouble for however long down the line, I think it maybe worth making the change (though we'd need some idea of scope to make that call). -- Rich
