On Tue, Oct 21, 2014 at 4:59 PM, Hunter Blanks <[email protected]> wrote: >> I'm a bit reticent to do this in the release candidate part of the >> release cycle, but we can get on it pronto for 0.9dev and apply the >> patch first before more interesting changes go in. I'd recommend, >> then, using that. >> > > That's fine by me. I've already got a package archive containing 0.8c1 and > its dependencies, so I don't think you should hold up the release while I > putter this out.
I hope you stick it out and make it happen anyway :) > That is a considerate choice, and indeed, when I first operationalized > WAL-E, I, too, reached for the Ubuntu system packages as a means for > installing WAL-E's deps. Sadly, some of the OpenStack dependencies didn't > line up with what was in Ubuntu 12.04 / 14.04. So it made more sense to > materialize all the dependencies into python packages (bdist_eggs. 2014 and > all, but really) and just follow a similar path to how we deploy other > Python environments. Yeah, I totally got when the new backends started coming in that it was going to screw up the debian-install-ability a bit fierce, but made the call to absorb this solvable loss in favor of multi-backend. I still think that is clearly the best for the longevity of this bit of infrastructure. -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
