Roland Mainz writes:
> > SVN support in tools, yes. In ON build, "huh."
>
> Well, the whole ksh93-integration stuff is done via Subversion since the
> beginning. I did one attempt to do some work with Mercurial long ago,
> lost the work of two weeks because Mercurial ate parts of the tree and
> then we never tried it again until today...
I don't think anyone is working on making ON's build system support
Subversion. It'd have limited utility as the gate itself is
Mercurial.
> > In the mean time, "touch usr/src/tools/findunref/exception_list.svn" (or
> > whatever which_scm reports for Subversion) should get you by.
>
> It seems I am getting "unknown" in this case (somehow the use of
> Subversion isn't detected properly... ;-( ) and I would need a file
> called "usr/src/tools/findunref/exception_list.unknown".
That's an interesting problem that needs some debugging in your
environment. What should be happening here is that the SCM_TYPE
variable should be set by the `nightly' script, and the findunref
Makefile uses this to figure out the right per-SCM exception_list.*
file.
The SCM_TYPE variable is gleaned from the `wstypes' function in
nightly, which uses the /opt/onbld/bin/which_scm script to detect the
type of SCM that's in use, and that *should* be able to detect
Subversion. It was tested with it.
Most curious about this sort of failure, though, is this code in the
wstypes function:
case "$child_type" in
none|subversion|teamware|mercurial)
;;
*) child_type=none
;;
esac
The current nightly script goes out of its way to make sure that
SCM_TYPE never ends up set to an unrecognized value. So how could it
be that you're running the current tools, but that you're somehow
getting SCM_TYPE set to "unknown"?
Is it possible that you're not using the current tool set?
--
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
