We've got a couple of priviate indexes for TG2, and were using them pretty extensively to make sure that there's a known good install with our current component set, but the number of components and the system creating indexes and installing from them makes this more complicated and frustrating than anybody likes.
But until all the kinks are worked out of some alternative system (like pip) we're stuck with it. So, here's a couple of proposed changes: 1) I'll be creating a new development index at: http://turbogears.org/2.0/downloads/dev/index/ This index will be built from whatever eggs are checked into the repository here: http://svn.turbogears.org/site_resources/tg2_index/current/ I'll also set both tg.devtools and the main turbogears2 eggs to use this index by default in setup.cfg. If we keep everything up to date this should make setup.py develop work on both turbogears2, and tg.devtools. We will have to remember to change that default when we do a release, so that releases install from their own stable index, but if those indexes are tested and kept stable that should not present any difficulty. Ultimately, I'm interested in using pip, but windows users will never like pip because it requires a compiler, and they likely won't have one. But ultimately I think it would be awesome to use Sanjiv's all in one windows installer for windows users, possibly including mingw so that they can compiler just like the rest of us. -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
