> For now, many people need to work on both the ON gate and the ON-STC{2}
> gates, which are not yet converted to mercurial. I know preparations
> are going on for opensourcing and conversion, but there has been no
> announcement yet. The SUNWonbld tools are officially required for that
> gate set for now. (Not to mention other gates that might be private and
> not yet converted, as mentioned by Jim.)
That seems like a poor design to me. The SUNWonbld tools are meant to
build ON. I can understand the desire not to reinvent the wheel, but the
fact is that there are a number of ON-specific things hardcoded into those
tools (e.g., the "OK warning messages" lists in nightly.sh), that simply
don't make sense in other environments (nevermind all the subtle and
undocumented dependencies between the Makefiles and the tools). Moreover,
it's untenable to require folks making changes to SUNWonbld tools to track
down every consolidation that also might be making use of the tools and
ensure that their changes are compatible.
I realize we're already in this mess. I'm just asking people to recognize
that this *is* a mess, and that ideally we should separate SUNWonbld from
a yet-nonexistent more generic SUNWbld package that would allow reuse.
But all of this is a separate conversation.
On a related note: I highly doubt there's anyone in sustaining who really
wants to make use of e.g. sccsrm given that it's been at least 5 years
since we allowed folks to remove files by moving them to .del-<foo> names.
Given that SCCS is dead in ON, it seems a good time to put the final nail
in the coffin for sccsrm, regardless of how long it takes us to kill the
rest of the old tools.
--
meem
