Current Supported Releases: Sablime^® v6.0 & v5.2

NAME
     nedges - generate version dependency graphs for SBCS or SCCS
     files

SYNOPSIS
     nedges [-n attr] [-T filt] s-file

DESCRIPTION
     nedges is used to print a version graph of an SBCS s-file by
     generating a dot(1) or dag(1) edge list from the s-file ver-
     sion information.

     The s-file version graph is a graph where  nodes  correspond
     to  versions  and  edges (arrows) indicate version dependen-
     cies.  The dot description must then be processed by the dot
     command  into  either  pic(1)  or, more commonly, PostScript
     output.  The output can be incorporated in  a  document  for
     printing.   The  details  of this process will depend on the
     user's environment.

OPTIONS
     -n attr
          There is single node attribute string made of label  or
          shape arguments.

          Label arguments:
               d date and time of version creation,
               p author (programmer) of version,
               r the version SID,
               s delta sequence number (chronological order).

          Shape arguments:
               b box,
               c circle,
               e ellipse,
               t plain text.

          The default node option is  -nrpe.   This  prints  each
          version's  SID  and author inside an ellipse.  With dag
          base version shapes are double circles,  and  with  dot
          their  shape  is  double the regular node shape (double
          box, ...), or double box if the regular node  is  plain
          text.

     -T filt
          Select the graph filter. The default is  dot,  but  dag
          can also be used.

               nedges s.file | dot -Tps > file.dot
               nedges -Tdag s.file | dag -Tps > file.dag

SBCS Release 1.2    Last change: 1 April 1994                   1

EXAMPLE
     The example in Figure 1 shows the delta content of  an  SCCS
     file  (s.sample_sc).  The graph was generated by nedges with
     default options and dot with PostScript option,  and  stored
     in  a  file edges.ps.  That file was then included into this
     man page and printed.

               $ nedges s.sample_sc | dot -Tps > edges.ps
               $ cat nedges.1
               ...
               .DS
               .\" file height width x-offset rotation
               .BP edges.ps 5.5i 6i 0 a0
               .EP
               ...
               $ troff -Tpost -man -mpictures nedges.1 | dpost -x+.1 -y-.3 | lpr

     Forward deltas, the only kind used by SCCS, are indicated by
     dashed  arrows.   To  retrieve version 1.1.2.10, SCCS starts
     from the base version 1.1 (double ellipse) and  applies  all
     the  1.1.2 branch deltas to it.  A nedges picture only shows
     the delta dependencies, and this picture says nothing  about
     the  size  of  deltas  and  does not clearly show their time
     sequence (delta 2.1.1.3 is actually later than 1.1.2.10, see
     the same example in sidtree(1)).

                         [PostScript Picture]

                   Figure 1: SCCS file s.sample_sc

     Figure 2 illustrates what happens to the SCCS file of Figure
     1  when  it  is  converted to the SBCS file s.sample_sb (see
     sc2sbcs(1)).  The delta dependency is altered and the branch
     versions  are  now  linked  by reverse deltas (solid lines).
     Many more base versions  (double  ellipses)  have  appeared,
     because  SBCS  turns zero size versions and those that would
     depend on them into base versions.  This has allowed all the
     branches  to  grow  using reverse deltas, carrying their own
     base version along.  Adjacent base versions  are  linked  by
     dotted  edges to help visualization, not to imply any depen-
     dency.

     To retrieve version 1.1.2.10 in this case is very fast:   it
     is  stored  in  the s-file compressed, but otherwise intact.
     The file used in this example was an SCCS file generated  by
     the  SABLIME product administration tool, and its trunk ver-
     sions are null.  SBCS always uses reverse deltas  along  the
     trunk,  but,  without  special conditions such as null trunk
     versions, branches normally use forward  deltas  (see  DELTA
     SCHEME in nadmin(1)).

SBCS Release 1.2    Last change: 1 April 1994                   2

                         [PostScript Picture]

                  Figure 2: An SBCS file s.sample_sb

BUGS
     When using dag, the arrows  for  reverse  deltas  point  the
     wrong way.  Use the more recent dot.

DIAGNOSTICS
     Warning and error messages have error codes that can be used
     with nhelp(1) for a more detailed explanation.

SEE ALSO
     , , nadmin(1),  ndelta(1),  nedges(1),  nget(1),
     nprs(1), sidtree(1).

SBCS Release 1.2    Last change: 1 April 1994                   3

Return to SBCS Commands manpage index