Changes between Version 7 and Version 8 of TracDev/PluginDevelopment
- Timestamp:
- Sep 17, 2005, 1:21:35 AM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/PluginDevelopment
v7 v8 68 68 == Packaging and deploying plugins == 69 69 70 Plugins are packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python Eggs]. You can use [http://peak.telecommunity.com/DevCenter/setuptools setuptools] to make a `setup.py` script that will produce a Python Egg for your plugin. 70 TracPlugins are packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python Eggs]. You can use [http://peak.telecommunity.com/DevCenter/setuptools setuptools] to make a `setup.py` script that will produce a Python Egg for your plugin. 71 71 72 72 73 The egg file needs to have a file named `trac_plugin.txt` in its `EGG-INFO` directory. This file should contain the names of all modules that need to be imported by Trac to register your components. 73 74 74 ''Note that this will change in the very near future: setuptools 0.6 will introduce the concept of “entry points”, which will be used instead of the `trac_plugin.txt` descriptor.'' 75 ''Note that this will change in the very near future: setuptools 0.6 will introduce the concept of “entry points”, which will be used instead of the `trac_plugin.txt` descriptor.''. See TracPlugins for details. 75 76 76 77 A plugin can either be deployed globally, or only for a specific environment. Global deployment is done by installing the plugin: … … 97 98 This will install an `.egg-link` file instead of the actual egg. That file is basically a link to the source directory of your plugin, so that Trac will always see the latest version of your code. 98 99 100 A tutorial to build your own plugins is available here: http://trac-hacks.swapoff.org/wiki/EggCookingTutorial 101 99 102 == Disabling built-in components == 100 103