I was confused by this, and I wouldn't consider myself a total newcomer -- maybe a partial newcomer. It seems like a checksum or hash could be check at the very least to compare the file or URL give at the command line and the cached file before anything is unpacked and installed.
-- Benjamin Jones On Mar 3, 2:08 pm, kcrisman <kcris...@gmail.com> wrote: > On Mar 3, 1:32 pm, Volker Braun <vbraun.n...@gmail.com> wrote: > > > On Thursday, March 3, 2011 6:19:01 PM UTC, Benjamin Jones wrote: > > > > You're right, it's not corrupted. I had to manually delete the .spkg > > > file in $SAGE_ROOT/spkg/optional and then run `./sage -f <URL>` again. > > > I consider this to be a bug in addition to a major trap for newcomers to > > fall into. If I manually specify a URL at the command line then its likely > > I'm testing a spkg and do NOT want to use a cached version. > > Yeah, I've run into that many times in the past while testing. I have > a feeling it's a feature rather than a bug for some reason, though you > are very right about it being a trap. -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
