13.3 Summary

1.

Patches should be kept as small as possible, ideally each patch representing a single bug fix or new element of functionality, and grouping together the minimum set of files needed.

2.

If a patch is subsequently found to have contained an error in perhaps only one file, an update patch can be prepared, which marks the earlier patch as a prerequisite. The parent/child mechanism should automatically avoid conflicts between the original and update patches.

3.

If it is wanted to thoroughly replace a patch, with a number of changed files, it is probably better to make a full replacement patch with the supercede stanza filled. The original patch is then not needed, and if it is installed, it will be removed by the new patch.

4.

Patch files form the basis for permanent adoption of new code into future versions of Molpro, and it is vitally important that the readme stanza describing the patch is filled in a helpful way.