On 10/25/10 11:35 PM, Robert Bradshaw wrote:
On Mon, Oct 25, 2010 at 3:04 PM, Dr. David Kirkby
I might have more of an issue with uploading binaries from my machine, as
the binaries are large and my "upload" bandwidth (which would be important
for uploading binaries), is only 1/8th of my download bandwidth. That might
be an issue for me.
If it's uploaded via script, just have it upload it overnight when
you're not online. If you can't upload a Sage binary in 8 hours
(=twice dial-up speed) then, yeah, you might have issues :)
Its not unusual for me to use the computer at night, so I'm not overly concerned
when the binaries were created.
One thing that would help a *LOT* would be if the binaries were created using a
decent compression method. The last Solaris binary I created was 500 MB using
gz, but that drops to 300 MB if 7zip is used instead.
http://www.7-zip.org/
But whilst a release manager will be build-testing quite
often, it is only rarely that binaries will be created - only one per Sage
release, so one a month or so.
Yep.
But even once/month, it would be nice to save 200 MB!
- Robert
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
