52 | | For general instructions about plugins, see also TracPlugins. |
53 | | |
54 | | The plugin egg can be added to the `plugins` folder of an existing environment, |
55 | | or to a brand new environment. Note that if you create a new environment, it's |
56 | | currently necessary to leave the repository directory '''empty''' during the |
57 | | `initenv` step (''this will probably be fixed soon''). |
58 | | |
59 | | Then, you need to specify which version control backend has to be used: |
| 52 | The configuration has to be done on the Trac side, |
| 53 | there's nothing to do on the Mercurial repository side, |
| 54 | except that it should be made available locally. |
| 55 | |
| 56 | === Setting up a Trac environment === |
| 57 | |
| 58 | You can either reuse an existing Trac environment, |
| 59 | or create a brand new one. |
| 60 | |
| 61 | For general instructions, see TracInstall. |
| 62 | |
| 63 | The TracAdmin `initenv` command has been slightly modified |
| 64 | in the vc-refactoring code base: in addition to the |
| 65 | ''repository directory'', it's also needed to specify the |
| 66 | ''repository type''. |
| 67 | |
| 68 | For the ''repository type'', specify `hg` instead of the default `svn`. |
| 69 | For the ''repository directory'', specify the location of the Mercurial repository. |
| 70 | |
| 71 | In all case, you [wiki:TracIni <trac_environment>/conf/trac.ini] configuration file |
| 72 | should have a `[trac]` section similar to the following: |
75 | | Finally, if you installed the egg by doing a `python setup.py install`, |
76 | | there's the additional constraint of specifically ''enabling'' the plugin: |
| 89 | === Setting up the mercurial plugin === |
| 90 | |
| 91 | The TracMercurial-0.1 plugin egg should be added to the `plugins` folder of the |
| 92 | environment. |
| 93 | |
| 94 | For general instructions about plugins, see also TracPlugins. |
| 95 | |
| 96 | Finally, if you installed an unpacked egg by doing a `python setup.py install` |
| 97 | (useful for development), there's the additional constraint of specifically |
| 98 | ''enabling'' the plugin: |