Maintenance Requirements

Once installed, the ChorusOS source code base must be maintained in its original state so that you can apply official patches and upgrade it as improvements become available.

Code that you have modified must not be mixed with the original (patched) code. Mixing modified code with the original code might make it impossible to support your installation. If you need to modify one of the original files, you should first create a copy of the entire source component in a new directory. You can then use the configure command with the -s option referencing this new directory, rather than referencing the original component directory.

Follow these guidelines so you can continue to patch and upgrade the installed source code as development proceeds:

Use source control tools.

Tools that help you handle file histories, lock access to files being updated and merge differing versions of the same file play an indispensable role in allowing you to maintain ChorusOS operating system source code alongside the version you are using to develop your product. One such set of tools, the Source Code Control System, is bundled with the Solaris^TM operating environment but many other products exist.

Maintain the installed source code separately from all modified code.

Once you mix your modifications with the original source code, there is no guarantee that it remains possible to patch the code. Furthermore, your support contract might not extend to modifications that you introduced into the source code.

Decide which tool chain you will use for development.

The ChorusOS operating system source code delivery does not include the source code for the cross compiler and accompanying tools used on the host to develop software for the target system. Use the binary tools provided with the source version of the ChorusOS operating system.

Apply patches on the original code in the source installation directory, and then propagate the modifications.

Modifications should be propagated to source trees, and merged into your potentially modified copies. Patches are verified to work only on the original (patched) source code base. See Chapter 5, Patches for more information about patching.