6282 ONBLD man pages not pbchk clean
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>

*** 19,38 ****
  .\" " CDDL HEADER END
  .\" "
  .\" "Copyright 2004 Sun Microsystems, Inc."
  .\" "All rights reserved"
  .\" "Use is subject to license terms."
! .TH WS 1ONBLD "28 January 1992"
  .SH NAME
  .I ws 
  \- enable SunOS avocet environments
  .SH SYNOPSIS
  .B ws
  [-e] [workspace_name]
- .LP
  .SH DESCRIPTION
- .IX "Avocet" "ws" "" "\fBws\fP"
  .LP
  .I Ws 
  will configure your environment to build the SunOS
  source base from an
  .I avocet
--- 19,36 ----
  .\" " CDDL HEADER END
  .\" "
  .\" "Copyright 2004 Sun Microsystems, Inc."
  .\" "All rights reserved"
  .\" "Use is subject to license terms."
! .TH WS 1ONBLD "Jan 28, 1992"
  .SH NAME
  .I ws
  \- enable SunOS avocet environments
  .SH SYNOPSIS
  .B ws
  [-e] [workspace_name]
  .SH DESCRIPTION
  .LP
  .I Ws
  will configure your environment to build the SunOS
  source base from an
  .I avocet
*** 101,118 ****
  endif
  .fi
  .RE
  .LP
  NOTE: this is a csh example, the code would vary with the shell type.
- .LP
  .SH OPTIONS
- .LP
  .TP
  .B \-e
  prevent ws from calling exit or exec, useful for setting environment in
  another Bourne (sh) compatible shell (hint: source ws -e)
- .LP
  .SH USAGE
  .LP
  At start-up time 
  .I ws 
  will determine the number of proto areas to
--- 99,113 ----
*** 189,199 ****
  The exception to this is if there is already an existing non-architecture
  specific populated proto area 
  under one of the PROTO{1-3} variables.  If this is the case then the
  ROOT and other flags will be based on that instead of an architecture
  specific sub-directory.
- .LP
  .SH ISSUES
  .LP
  The use of Constrained Files is very different between an NSE
  environment and an avocet workspace.  Constrained files are files which
  are derived but files that you do not have source code for.  For
--- 184,193 ----
*** 235,245 ****
  of a full proto area and contain only those files which you are concerned
  about.  Both of these methods would protect you from updates to files
  because you would be in full control of the proto areas you are linking
  against.  It would be your responsiblity to update your proto area
  as your work progressed.
- .LP
  .SH EXAMPLES
  .LP
  In the following examples you will modify the 
  ${CODEMGR_WS}/avocet/sunos/protodefs file to define PROTO{1-3}
  to configure a proto hierarchy to be associated with your
--- 229,238 ----
*** 349,367 ****
  .LP
  This model differs from the one above in that we can not reference
  the parents proto area because the parent in an NSE environment.  
  Instead for our second proto area we point to a stable proto
  area outside of the NSE.
- .LP
  .SH ENVIRONMENT VARIABLES
  .LP
  Here is a list of the environment variables that 
  .I ws
  will set and how they are used:
  .LP
  CODEMGR_WS         
- .fi
  .RS 5
  Absolute pathname to the Avocet workspace.  This environment variable
  is referenced by the
  .I bringover
  ,
--- 342,358 ----
*** 411,434 ****
  .RS 5
  This set of environment variables is used to set the LDLIBS.master
  macro within the SunOS source tree.  These values usually point
  to a hierarchy of directories to search for libraries.
  .RE
- .LP
  .SH FILES
  .LP
  .nf
  $CODEMGR_WS/avocet/sunos/protodefs
  .fi
- .LP
  .SH "SEE ALSO"
  .LP
  .IR workspace (1),
  .IR bringover (1ONBLD),
  .IR putback (1),
  .IR protodefs(5)
- .LP
  .SH BUGS
  .LP
  TERMPROTO is broken.
  On 5.x builds TERMPROTO is incompatible with the C++ driver.  The bug
  is that the C++ driver does not use the standard SVR4 notation
--- 402,422 ----