On Tuesday 04 August 2009 02:50:05 Jd wrote: > From what I gather, TG2 installation puts together a bunch of cool > projects together in the right way for them to be extremely useful. We > have chosen it for our project. > > Now the problem is that we would like to freeze these components that > it come with. Everytime I install a new tg2env and TG2 in from the > instructions, I get different version of the stuff. Also these seem to > differ on different linux distributions (CentOS, Fedora, Ubuntu etc) > > We would like to have one environment that refers to specific > versions of the underlying components. > > What we would like to see is... > -- TG2.0 --> component1 (v2.2), component2 (4.5.3) > -- TG2.1 --> component1 (v2.3), component2 (4.5.3) > > Is my understanding off ? > Any suggestions or more explanation on how things are put > together ?
You can achieve this by creating a custom index-page that you restrict easy_install to use when fetching eggs to install. For that, put a line like [easy_install] find_links = http://eggbasket.office.ableton.com/versionset/81 allow_hosts = eggbasket.office.ableton.com into setup.cfg parallel to setup.py in your project. We do so by having a customizied EggBasket that supports a thing we call versionsets. And a commandline-tool called Easterbunny that uploads a virtualenv as whole, making it one of those versionsets. This works extremely smooth for us for a year now. Other options also exist, zc.buildout works also AFAIK, but I never toyed around with that. diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
