Am 05.12.2011 15:03, schrieb Alessandro Molina:
Any other idea on how to avoid people having to manage a hube bunch of packages they really don't care about?
We could add upper limits to the version numbers in addition to the lower limits.
Sure, in reality, even slight changes can break a TG project. For instance, I found some of my apps were broken when updating repoze.who.plugins.sa from 1.0rc2 to 1.0 (http://github.com/repoze/repoze.who-sqlalchemy/issues/1) and it took me quite some time to identify the cause. Some small changes can have a big effect.
Can we keep both available? The local index and the precise version? So that both ways work.
That would be an option. One problem is that we must differentiate between the requirements of TG itself and the requirements of the TG project. The former are maintained by us, the latter by the project maintainer. And the more restrictions we have, the easier they can get at odds with each other when updating TG.
-- Christoph -- 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.
