James Carlson wrote:
> [EMAIL PROTECTED] writes:
>
>>> It was originally a Sun tool that was specific to OpenSolaris but is now
>>> opensource that anyone can install and use.
>>>
>>>
>> So, to install and use it I need to read the source code?
>>
>
> No. Just install the SUNWonbld package, and you'll have the ON tools
> (including webrev) in /opt/onbld/bin.
>
> The SCM Migration page has an updated version of this package that
> supports Mercurial, but there are others.
>
>
>> I used it
>> once back in September. I tried again to
>> use it this past weekend with dismal results.
>>
>
> Without knowing what "dismal" means here or what you did or what
> problems you might have had, it's hard to comment other than to say
> that it "works for me."
>
>
>> Is there a cookbook for
>> using it? Or are you supposed to re-install
>> it every time you upgrade your system? Or is the preferred method to
>> sit with someone who knows how
>> to use it, and learn from them?
>>
>
> No, you shouldn't have to reinstall it.
>
>
Thanks James (and Richard). I run webrev and get:
bash-3.2$ webrev
Unable to determine SCM type currently in use.
For teamware: webrev looks for $CODEMGR_WS either in
the environment or in the file list.
bash-3.2$
Then I try using a file list:
bash-3.2$ cat file.list
CODEMGR_WS=/lenovahd/max/onnv-gate
usr/src/cmd/zdb/zdb.c
bash-3.2$
bash-3.2$ webrev file.list
SCM detected: teamware
File list from: file.list
/opt/onbld/bin/webrev[1712]: workspace: not found
: no such parent workspace
bash-3.2$
I guess I don't have a workspace. /lenovahd/max/onnv-gate is downloaded
from mercurial. Is there
something else I am supposed to do to set up a workspace? I went
through this before back in
September, and got it to work eventually (with help from people here).
thanks,
max
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
