I have the habit of installing a short list of optional spkgs whenever I build a new Sage version on my machine, and to avoid downloads I have been keeping the .spkg files locally, and using sage -i <path>/xxx.spkg
I realise that this will probably not work (or will it?) with the the git arrangement, e.g. if I have just built Sage from the distribution tarball sage-6.0.tar.gz. Is there still a way of keeping optional spkgs locally? And surely this should have worked: $ sage -version Sage Version 6.0, Release Date: 2013-12-17 $ sage -i database_cremona_ellcurve Found local metadata for database_cremona_ellcurve-20121022 Attempting to download package database_cremona_ellcurve-20121022 >>> Trying to download >>> http://www.sagemath.org/packages/upstream//database_cremona_ellcurve/database_cremona_ellcurve-20121022.tar.bz2 [............................................................] Checksum: 863a961d723a558fa5d732c24292f63aa5158752 vs 2ea3d7f20ff4015da050326b6e2395977b4ce4c9 Invalid checksum for database_cremona_ellcurve-20121022.tar.bz2.tmp For me, this particular spkg is definitely *not* optional! John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
