Peter Memishian writes: > > > > On vaguely related note: is there some reason sccsrm (or and the sccs* > > > commands in general) are still in $BUILD_TOOLS/onbld/bin? Seems like an > > > attractive nuisance. > > > > Several people have told me that people tend to use tools from one > > release on another /ws/onnv-tools on on10-patch, or the like. > > Using the wrong tools for a given gate is downright dangerous. We have > e.g. /ws/on10-patch-tools for a reason. We are asking for trouble by > leaving land mines like wx adrift in /ws/onnv-tools past their use-by > date.
I don't disagree. We made an intentional decision, though, to keep those tools for now. First of all, not everyone has converted yet or will convert by the end of today. It seems almost inevitable that there will be project teams using public build machines with the new tools where the Nevada-based ON project gate hasn't been sync'd since snv_96, and won't be sync'd again for weeks or months. Supporting them until they're ready to switch (or dragged into it, as the case may be) seems like a worthwhile thing to do. Secondly, those old tools all fail if tried in a Mercurial workspace, with the lone possible exception of "sccs create". (I don't think we can help you if you do that; that's not an internal tool.) Thus, they're generally not actively harmful. And, finally, Rich is right: there are folks who use tools from one gate while working on another, no matter how inadvisable it seems. I ran into this when I was doing the non-root build work (there was one gatekeeper who was particularly adamant on the point that traditional root builds must always continue to be supported in new tools so those tools can be used with older gates), and not running into that kind of opposition and extended debate again seems to me like goodness. Having an RFE to remove these stale things (including wx and sccsrm) some point down the road sounds like a good thing to me, but I doubt that it's the right choice now. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
