I'm currently working on ticket #329 My idea is adding to each .spkg file a .spkg.md5 file with the md5checksum This should prevent file corruption.
I've already reimplemented the md5sum standard utility (from the coreutils package) in python (using the md5 module), so that we don't need to add an extra dependency to sage. I still have to modify the logic of the scripts (sage-download-package, etc.) so that they do the right thing. Pablo On 10/20/07, Timothy Clemans <[EMAIL PROTECTED]> wrote: > > Hi, > > I think I have done "sage -upgrade" a few times when William was in > the process of uploading a new release. I think it would be helpful if > Sage would check a file on sagemath that gave the latest release that > had been completed uploaded. Another possibility might be that William > would upload the files to directories that Sage doesn't look in and > then move them over to the release directories after they have been > completely uploaded. > > Timothy > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
