The index is required right now, but that will change in the future.
I did use it in the example in the e-mail, so it's not like it was
undocumented, but yea, it will be nice when it's not required anymore.

If we required a higher version of repoze.who that would update
automatically, but rather than force updates on people 2.0.2 provided
the minumum change that people needed to get bugs fixed and the
security holes patched.

We will likely make a metapackage in the future that has all the
dependencies and pushes them to the latest version so that we can do a
-U on that directly.

On Thu, Aug 13, 2009 at 11:40 AM, Derick
Eisenhardt<[email protected]> wrote:
>
> This upgrade system doesn't seem to work very well, or at least not as
> expected. First off, it needs to be:
>
> easy_install -Ui http://turbogears.org/2.0/downloads/current/index/
> TurboGears2
>
> to actually pull 2.0.3, without index in the URL it doesn't seem to
> really do anything. Secondly it only updates that one package, but
> none of its dependencies...after preforming both versions, my Repoze
> installed is still at 1.0.10, when it should be now at 1.0.15.
> Personally, I'm just gonna do a new virtual environment with a fresh
> install...but would be nice to be able to upgrade All :/
>
>
> On Aug 12, 7:09 am, Mark Ramm <[email protected]> wrote:
>> I messed up the 2.0.2 egg in an svn merge mistake, so we've now
>> relesed 2.0.3 with a fix.  Install instructions are the same.
>>
>> easy_install -Uihttp://turbogears.org/2.0/downloads/current/TurboGears2
> >
>



-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to