Next: Environment, Previous: File Format, Up: Top [Contents][Index]
This part of the CSSC manual describes how CSSC interoperates with SCCS. For the enormous majority of cases, this occurs seamlessly; however sometimes it is not possible for CSSC to pick “one right way” to proceed unaided. Circumstances where this occurs are described in detail, below.
In order to interoperate better with other implementations of SCCS, the CSSC suite can also be configured to turn off several features which provide flexibility beyond that which is available in some other implementations of SCCS. Some other interoperability features of CSSC exist to maintain compatibility but do not need to be turned off.
| • Binary File Support: | Enabling or disabling support for binary files. | |
| • Executable File Support: | Support for a SCO extension. | |
| • BitKeeper: | Limited support for Bitkeeper files exists. | |
| • Maximum Line Length: | Limiting the length of lines in the SCCS file. | |
| • Limitations of diff: | Diff has limits too, on many non-GNU systems. | |
| • Configuration: | Viewing the current configuration. | |
| • Bug-for-Bug: | We go to great lengths to be compatible | |
| • Incompatibilities: | Sometimes we cannot be fully compatible | |
| • SCCS Version Differences: | Versions of SCCS behave inconsistently | |
| • CSSC Extensions: | Behaviour which is specific to CSSC. |