I am considering updating my tracs install from the 0.12 multirepos from 2008-09-09 (when I installed it was current at the time) to the current version. Although I use tracs daily, I do not update so very often. Is there a guide to doing this correct? Would these steps be adequate:
- Stop tracs logins - Back up current tracs env - Back up the tracs parts in /usr/lib/python/site-packages/ Trac-0.12multirepos-py2.5.egg, where I guess all of tracs lives. - Install the new 0.12 multirepos tracs from svn - Check for any diffs in the tracs.ini file - Enable tracs logins - Enjoy One thing that made me stop and ask this question was that I see I have an older tracs in /usr/lib/python/site-packages/Trac-0.11.1- py2.5.egg. I remember starting with this one and then later upgrading to 0.12 multirepos, but I do not recall what I did to make Trac-0.12multirepos-py2.5.egg be used instead of Trac-0.11.1- py2.5.egg. Age... After installing the new 0.12 multirepos, should I need to do anything to get it to be used? Based on the names I see, I am guessing the update will replace the existing Trac-0.12multirepos- py2.5.egg. I have been following the development of tracs and see that there are new features being added that would make my tracs experience even better (things like render user variable text, use user variable descriptions instead of the variable name as labels). Is it the plan that the multirepos branch be fully merged with the trunk so it gets all these nifty new features? Or will the multirepos remain a branch? Just curious. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
