Thanks, Noah. It does appear that I should (if I am understanding the documentation) use VirtualEnv to create isolated Python environments for different applications. The idea being that I can set up one VirtualEnv install the dependencies for my Trac 0.10 install and then another VirtualEnv for Trac 0.11, correct? I'm not quite sure how this all plays with Apache vs. tracd, but I'll walk through the documentation and if I have any further questions, I'll post back. (Any gotchas that you see up front if you could call to my attention would be appreciated, however)
As a tangential question, what have people done using Trac 0.10.x to get around the problems that spawned configurableWorkflow in Trac 0.11? Specifically I have a newly minted QA guy who wants to have issue tickets move to a QA queue of sorts. Obviously this is handled in Trac 0.11, but at least in one case they "need" the PrivateTicketPlugin which, last I looked was only still available at 0.10.x. My recommendation to my client if they needed the PrivateTicketPlugin that was only available for 0.10 was to either contact coderanger and bribe him or just instill in the engineers the workflow of assigning their tickets to a QA user for validation - it being a small company that seemed realistic. Was wondering if anyone else in the community had other suggestions around that if they absolutely positively couldn't live without some plugin that hadn't made the 0.11 leap yet? Vincent On Apr 8, 2:06 pm, Noah Kantrowitz <[EMAIL PROTECTED]> wrote: > Vincent Polite wrote: > > Hello all, posting under a new email address. Hope all is well in the > > Trac universe. I have a question. There are two "vectors" of > > approach that I would like to discuss. > > > What is the "best way" to put Trac 0.10 and Trac 0.11 on the same > > machine. It seems that the versions of python and other dependencies > > are different for both of these versions; obviously the templating > > engine change is huge. I have a client who wants the > > PrivateTicketPlugin on one Trac instance but can't live without > > CustomWorkFlow on the other instance. I've looked a bit through > > google in an attempt to find a how-to for installing concurrent > > versions of Trac on a machine and was wondering if someone could point > > me to the right documentation if such an animal actually exists --- > > or, if it doesn't exist, maybe a discussion on what would be required. > > Look up virtualenv. OS X 10.5 already comes with the major dependencies, > so all you should need to install in the virtualenv for 0.11 is Trac and > Genshi. Even just `easy_install Trac==0.11b2` should do it. > > --Noah > > signature.asc > 1KDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
