Am 20.08.2009 17:14, schrieb Ryan Booz:
Would be happy to try the easy_install - the only problem is I'm doing this on my main Trac server since I already have a number of projects setup. If I do the easy_install - won't that effect my current Trac options? Or, will it just become an egg plugin that I can selectively load in each project?
Actually it is like this:However trac finds a trac plugin (uploaded egg, somewhere in site-packages, ...), it will show it in Admin/Plugins. You can choose to enable or disable it by environment.
However due to some design decisions in Python, you can not use two different versions of the same plugin in two different environments if you use the same trac process.
In that respect installing Agilo by egg upload is no different to easy_installing it.
But I want to note that this is essentially what we call a "mixed-environment" (Agilo + non-agilo environments in the same process). Because trac lacks some extension functionality for us, we need to do some run-time patching. We tried our best to hide when we're in an environment which has no Agilo enabled and we went great lengths to ensure that we don't interfere with standard trac environments. (Theoretically other plugins might have this effect as well...)
So probably everything will work fine for all other environments even if you install Agilo. If your business depends on it, try the virtual machine for experimentation.
fs
smime.p7s
Description: S/MIME Cryptographic Signature
