Sun WorkShop TeamWare 2.1 Release Notes Page 1 1. Sun WorkShop TeamWare 2.1 Release Notes These release notes provide you with last-minute news and supplemental information about the Sun WorkShop TeamWare 2.1 Release. The READ_ME_FIRST file located on the Sun WorkShop 5.0 Web site and on the product CD (/cdrom/devpro_v6n1_/READ_ME_FIRST) contains later information than these release notes. What's New? * Building * DistributedMake * Merging * Versioning * Freezepointing Software Notes List of known problems and special features of this TeamWare version. Documentation List of documentation sources, where to find information such as README's, patches, system requirements, and errata. To contact us, choose Help--> Send Comments in any of the TeamWare main windows. Sun WorkShop TeamWare 2.1 Release Notes Page 2 2. What's New? * Building * DistributedMake * Merging * Versioning 2.1. Building * A new options dialog in the dmake Jobs Graph provides a straightforward way to adjust the time axis units to accommodate different job durations. Time may be displayed in seconds, minutes, or hours with a handy one-step menu selection to display total elapsed time at any point during the build. In addition, the time axis may be scrolled at any time while a build is in progress to review completed job status. * The process of defining build macros and environment variables from within the Target Editor has now been made more convenient by providing an extended ``browsing'' pane that shows current macro or environment variable definitions. The list of environment variables is imported from the Sun WorkShop environment while the list of macros is imported from the current makefile. Usage Note If you use a script to run a build, you should build outside of Workshop. Make sure your makefile assumes that the compiler output is piped to another tool and processed in parallel. 2.2. DistributedMake * Distributed Make (dmake) now provides the ability to specify a different dmake execution path for each build server. The default behavior is to assume that the dmake support binaries are located on the build server in the same logical path as the dmake host. Alternate paths for build servers may be specified in the ~/.dmakerc file as a host attribute. For example: group sparc_cluster { Sun WorkShop TeamWare 2.1 Release Notes Page 3 host wren { jobs = 10 , path = "/set/dist/sparc-S2/bin" } host stimpy { path = "/opt/SUNWspro/bin" } } * The names of groups and hosts specified in the ~/.dmakerc file may be enclosed in double quotes. This is to allow more flexibility with respect to the character sequences that may appear as part of the group and host names. For example, if the name of the group starts with a digit it should be double-quoted: group "123_sparc" * A new special target is now recognized by Distributed Make (dmake) to force execution of a given task to occur on the local host (the system from which dmake was invoked). If the special target called .LOCAL is defined in the makefile, dmake processes all its dependencies serially (similar to the .NO_PARALLEL target) on the local host. Consider the following makefile segment: .LOCAL : $(PROG) $(PROG) : $(OBJ) $(LINK) -o $@ $(OBJ) In this case, target $(PROG) will be built on a local machine while $(OBJ) targets can be build on different hosts. Usage Note OS levels and architectures of the multiple remote build servers should be the same. In addition, all files required by DMake must be accessible from all machines selected. 2.3. Merging * The display performance has been vastly improved. This is especially evident when merging very large files. * Merging now provides enhanced navigation features to facilitate the merging process. Both ``diff navigation'' options and text navigation options are available from the Navigate menu, and also by popup menu from clicking the right mouse button on any of the three Merging text panes. New text navigation features include the ability to search for a given text string, display the current line number(s), and go to a specific line number. * New options have been added to Merging allowing customization of Sun WorkShop TeamWare 2.1 Release Notes Page 4 tab stops, and control over diff behavior. For example, the differencing engine can be directed to ignore letter case and/or trailing or embedded white space. These new options are available from the Merging Options menu. * The Reload button is now added to the Merging window when Merging is invoked by a Resolve transaction in Configuring. This button lets you ask Merging to abandon all edits that have been performed on the two files and reload them from disk, and to automatically resolve any non-conflicting differences if the Auto Merge option is selected. * There is no longer a limit of 4096 characters on the length of lines in the files being merged. 2.4. Versioning * The display performance of Versioning has been vastly improved. This is especially evident when viewing directories with a large number of files under SCCS control, or showing the delta tree of a file with an extensive SCCS history. * New features have been added to Versioning that provide the ability to scan the entire workspace for checked-out files or for history files that contain unmerged deltas. These new options are available from the Workspace/Find...menu selection. These operations are also available from the new 'find' subcommand of the 'workspace' command-line utility (see below). In addition, the Versioning History window now provides the ability to highlight removed or unmerged deltas. * Versioning now provides the ability to merge branch deltas that were left unmerged by previous SCCS or TeamWare operations. To invoke this feature, you must first show the version history for a file, and then select two versions that you wish to merge. Click the right mouse button in the History window to bring up a popup menu that offers a Merge Branches...option. 2.5. Freezepointing * The Freezepointing extract operation now provides an option to create TeamWare workspaces from the freezepoint file. The user may choose to extract the complete set of ``frozen'' files or a subset Sun WorkShop TeamWare 2.1 Release Notes Page 5 thereof. * The extract operation may now be performed on an existing destination directory. A warning dialog is displayed requesting confirmation before proceeding. * A new option has been added to the Freezepointing create operation to update an existing freezepoint file rather than creating a new one. * The new command ``freezept diff file1 file2'' has been added that allows the user to compare two freezepoint files. Sun WorkShop TeamWare 2.1 Release Notes Page 6 3. Software Notes TeamWare SCCS Restrictions Lists the sccs subcommands to avoid in TeamWare workspaces. 3.1. TeamWare SCCS Restrictions Avoid using the sccs subcommands cdc, comb, fix, and rmdel in TeamWare workspaces. Using these commands can alter SCCS history files in ways which will make them impossible for TeamWare to track. These commands also have undesirable side effects when used on files that exist in multiple workspaces that eventually may be merged. cdc Can cause unnecessary branching and confusing histories. comb Completely rebuilds the SCCS history file. fix A front-end for rmdel. rmdel SCCS restricts the use of the rmdel command to remove only the most recent (leaf) delta on a branch. If you remove a delta that also exists in another workspace, it is possible that another user will add a delta in the other workspace. The delta that was removed in your workspace will no longer be a leaf delta when the files are merged. Sun WorkShop TeamWare 2.1 Release Notes Page 7 4. Documentation Where is? Documentation See the online help and the man pages. README's Check the install directory: /SUNWspro/READMEs/tw_release_notes where the default is /opt. Patches Look in the Patch directory on the CD. System Requirements In the Sun WorkShop Quick Install manual, on the Sun WorkShop 5.0 Web page, and in the READ_ME_FIRST file on the Web page and on the product CD at /cdrom/devpro_v6n1_READ_ME_FIRST. Recommended Compilers In the Sun WorkShop Quick Install manual. Registration See Help--> About TeamWare.