5 | | 1) The one-to-one association between a file and its RCS version (,v) file is used by the Miriad makefiles to define rules that |
6 | | keep the plain-text sources up-to-date automatically. These rules are used explicitly when rebuilding the system and |
7 | | implicitly in the dependency analysis. For example, an included header file (.h) is checked out automatically if necessary, even if it resides in a different directory, simply by appearing as a dependency of the target. Without a one-to-one association, there is no way to implement these rules in svn. |
| 5 | 1) The one-to-one association between a file and its RCS version (,v) file is used by the Miriad makefiles to define rules that keep the plain-text sources up-to-date automatically. These rules are used explicitly when rebuilding the system and implicitly in the dependency analysis. For example, an included header file (.h) is checked out automatically if necessary, even if it resides in a different directory, simply by appearing as a dependency of the target. Without a one-to-one association, there is no way to implement these rules in svn. |