39 | | will check out the documentation, web presentation, and test folder in a similar way. With FCM (see below), the |
40 | | above checkout commands would be somewhat simpler: |
41 | | {{{ |
42 | | fcm co fcm:ropp_src_tr ropp_src |
43 | | fcm co fcm:ropp_doc_tr ropp_doc |
44 | | fcm co fcm:ropp_web_tr ropp_web |
45 | | fcm co fcm:ropp_test_tr ropp_test |
46 | | }}} |
47 | | The latter requires that FCM is set up properly in your environment. |
48 | | |
49 | | |
50 | | == About FCM == |
51 | | |
52 | | [http://www-nwp/~frtc/FCM/trunk/doc/sys/user_guide/index.html FCM] (Flexible Configuration Management |
53 | | system) is the Met Office's set of tools build around Subversion (for version management), Trac |
54 | | (for issue tracking) and the Met Office's own build system. ROPP uses FCM only for code management; the |
55 | | build part is based on GNU's autotools. The |
56 | | [http://www-nwp/~frtc/FCM/trunk/doc/sys/user_guide/index.html documentation for FCM] is quite exhaustive; |
57 | | to access the FCM commands the following command needs to be added to your .profile (or equivalent shell |
58 | | initialisation file): |
59 | | |
60 | | {{{ |
61 | | . ~frdm/FCM/bin/env.sh |
62 | | }}} |
63 | | |
64 | | Among the advantages of using FCM is a simpler frontend to Subversion commands (see the checkout examples above), |
65 | | but also and graphical diff and merge utilities. In order to support ROPP, the following abbreviations/keywords |
66 | | are implemented within FCM: |
67 | | |
68 | | {{{ |
69 | | fcm:ropp_doc svn://eld001/ROPP_svn/ropp_doc |
70 | | fcm:ropp_doc_tr svn://eld001/ROPP_svn/ropp_doc/trunk |
71 | | fcm:ropp_doc_br svn://eld001/ROPP_svn/ropp_doc/branches |
72 | | fcm:ropp_doc_tg svn://eld001/ROPP_svn/ropp_doc/tags |
73 | | fcm:ropp_src svn://eld001/ROPP_svn/ropp_src |
74 | | fcm:ropp_src_tr svn://eld001/ROPP_svn/ropp_src/trunk |
75 | | fcm:ropp_src_br svn://eld001/ROPP_svn/ropp_src/branches |
76 | | fcm:ropp_src_tg svn://eld001/ROPP_svn/ropp_src/tags |
77 | | fcm:ropp_test svn://eld001/ROPP_svn/ropp_test |
78 | | fcm:ropp_test_tr svn://eld001/ROPP_svn/ropp_test/trunk |
79 | | fcm:ropp_test_br svn://eld001/ROPP_svn/ropp_test/branches |
80 | | fcm:ropp_test_tg svn://eld001/ROPP_svn/ropp_test/tags |
81 | | fcm:ropp_web svn://eld001/ROPP_svn/ropp_web |
82 | | fcm:ropp_web_tr svn://eld001/ROPP_svn/ropp_web/trunk |
83 | | fcm:ropp_web_br svn://eld001/ROPP_svn/ropp_web/branches |
84 | | fcm:ropp_web_tg svn://eld001/ROPP_svn/ropp_web/tags |
85 | | }}} |
86 | | |
| 39 | will check out the documentation, web presentation, and test folder in a similar way. |
110 | | It is possible to configure Trac to better fit this project, especially in regard to ''components'', |
111 | | ''versions'' and ''milestones''. At present, however, this is only possible on a system administrator level; |
112 | | so contact Dave Matthews about such changes. |
| 63 | It is possible to configure Trac to better fit this project, especially in regard to ''components'', ''versions'' and ''milestones''. Unfortunately, this is only possible on a system administrator level; please contact me (christian AT marquardt DOT sc) about this. |