Thanks for the tip Mike. I'll investigate this approach and report progress,
if I make some.
Carlos
2009/11/24 Mike Hansen mhan...@gmail.com
Another option might be using a unionfs overlay to monitor the files
that get installed / changed during the installation of an spkg. I'm
not sure
On Nov 23, 4:51 pm, Carlos Córdoba ccordob...@gmail.com wrote:
I think it's a bit cumbersome to download 400-500 gigs
and uncompress this big tarball every month - two months, especially for
people with old computers, small hard drives and/or who live in developing
countries where internet
Harald Schilly wrote:
On Nov 23, 4:51 pm, Carlos Córdoba ccordob...@gmail.com wrote:
I think it's a bit cumbersome to download 400-500 gigs
and uncompress this big tarball every month - two months, especially for
people with old computers, small hard drives and/or who live in developing
On Mon, Nov 23, 2009 at 9:24 AM, Jason Grout
jason-s...@creativetrax.com wrote:
Harald Schilly wrote:
On Nov 23, 4:51 pm, Carlos Córdoba ccordob...@gmail.com wrote:
I think it's a bit cumbersome to download 400-500 gigs
and uncompress this big tarball every month - two months, especially for
William Stein wrote:
(3) Any changes or customizations the user makes anywhere to their
sage install will be *deleted*.
I think (3) is perhaps the biggest issue.
I think emphasizing that this is a binary upgrade and *only* works to
overwrite your current sage directory to an exact copy of
On Tue, Nov 24, 2009 at 12:39 AM, Jason Grout
jason-s...@creativetrax.com wrote:
Note that doing the rsync (to a copy of your current sage directory) is
no different than downloading the binary and untarring it, but
presumably it is quite a bit faster and requires less bandwidth.
However, it
On Mon, Nov 23, 2009 at 9:39 AM, Jason Grout
jason-s...@creativetrax.com wrote:
William Stein wrote:
(3) Any changes or customizations the user makes anywhere to their
sage install will be *deleted*.
I think (3) is perhaps the biggest issue.
I think emphasizing that this is a binary
William Stein wrote:
On Mon, Nov 23, 2009 at 9:39 AM, Jason Grout
jason-s...@creativetrax.com wrote:
William Stein wrote:
(3) Any changes or customizations the user makes anywhere to their
sage install will be *deleted*.
I think (3) is perhaps the biggest issue.
I think emphasizing that
On Nov 23, 6:24 pm, Jason Grout jason-s...@creativetrax.com wrote:
rsync
I think you mean rdiff-backup and I was thinking about bsdiff/bspatch.
About rsync, If you have problems downloading a big file, you will
even have more troubles doing rsync since it scans all 150,000 files
of sage and
An xdelta or something like that, which could be joined with a previous
tarball to form the latest release would be great.
Besides, wouldn't it be possible to create binary spkg's that instead of
containing the source code would contain the binaries and data which result
after compilation? You
On Mon, 23 Nov 2009 at 11:24AM -0600, Jason Grout wrote:
What if we just keep build directories on sage.math? Then people can
use rsync to update their binary installations, which is an intelligent
binary diff program providing compressed differentials.
So we can just have a directory
On Mon, Nov 23, 2009 at 3:32 PM, Dan Drake dr...@kaist.edu wrote:
On Mon, 23 Nov 2009 at 11:24AM -0600, Jason Grout wrote:
What if we just keep build directories on sage.math? Then people can
use rsync to update their binary installations, which is an intelligent
binary diff program providing
On Mon, 23 Nov 2009 at 03:55PM -0800, William Stein wrote:
A compromise between tarball on a webserver and rsync server is
zsync: http://zsync.moria.org.uk/
zsync is a file transfer program. It allows you to download a file from
a remote server, where you have a copy of an older version
On Mon, Nov 23, 2009 at 6:08 PM, Dan Drake dr...@kaist.edu wrote:
On Mon, 23 Nov 2009 at 03:55PM -0800, William Stein wrote:
A compromise between tarball on a webserver and rsync server is
zsync: http://zsync.moria.org.uk/
zsync is a file transfer program. It allows you to download a file
William,
I think what Dan is proposing is just to use an old tarball and an
intelligent algorithm to auto-magically recreate the latest one. Then the
user would have to uncompress it so he/she could use the new sage. I don't
think this could be done inside sage itself.
2009/11/23 William Stein
Another option might be using a unionfs overlay to monitor the files
that get installed / changed during the installation of an spkg. I'm
not sure about deleted files, but spkg which for example delete the
old copy before installation could have that functionality factored
out into a spkg-clean
16 matches
Mail list logo
