[Yt-dev] binaries

[Matthew Turk]

Hi guys,

I just re-read this old post by Corey Goldberg:

http://coreygoldberg.blogspot.com/2008/09/test-tools-open-source-feedback-and.html

and I was wondering which systems you've installed yt on.

I've done it on OSX, which I don't think we can package easily (but
I'm checking into that, since it's almost all binary installers in the
install_script_osx.sh now...) x86_64 on a couple different
architectures, and I think that's it.  I was wondering what you all
thought about providing binary tarballs of the results of
install_script.sh for kraken (non-CNL, as I think perhaps for now --
until the parallel stuff is documented -- we want a slight barrier to
entry to that), ranger, abe and others I might be forgetting?

I have the bandwidth & space to spare, I do believe.  At current
rates, I'm estimated to use 11GB out of my 7TB of bandwidth for March.
 (I think a large portion of that is actually LCATest downloading the
yt repo every time it checks out enzo.)  yt.e.o itself uses ~100MB of
b/w a day, which could be mirrored dependencies or could be just the
images in the gallery hit a bunch of times.  I dunno.

If we wanted to provide these tarballs, we'd have to use virtualenv:

http://pypi.python.org/pypi/virtualenv

and make the environment relocatable.  This is ... not hard.  What do
you all think?  I'd need some help with this.

-Matt