Open Stack

It does seem sad that the state of package management is this bad. 

It'd would be equally interesting to hear how others rollback changes (another thing yum doesn't do so well, since it doesn't have a good ability to rollback dependent changes, especially when said rollback would alter a lot of versions and requirements). Maybe apt does this better. Idk.

How are others working through that? 

Sent from my really tiny device...

On Aug 6, 2013, at 11:57 AM, "Clint Byrum" <clint at fewbar.com> wrote:

> Excerpts from Dean Troyer's message of 2013-08-05 10:03:07 -0700:
>> * about-face on all-packages to all-PyPI (mtaylor): I'm still on the
>> use packages where possible side but DevStack specifically is not in
>> the packaging business.  If it were we'd do what Java folk (*sorry*)
>> have long taken the approach for non-trivial apps to just include the
>> whole damn runtime.  Write once duplicate everywhere.
> 
> Just as an FYI, we have gone with the virtualenv + pypi for everything
> approach in TripleO. Each project gets its own virtualenv and its own
> isolated python path.
> 
> This has exposed a few problems (most recently Heat was broken without
> at least one thing that pulled in Babel in its virtualenv because it did
> not explicitly list Babel in requirements.txt), but these are straight
> forward and need fixing anyway.
> 
> I was a bit resistant to this approach at first, but this has produced
> a very simple system that is also isolated from the python oddities of
> any system level tools.
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev