On Mar 2, 11:21 am, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > The current code in sage-spkg to determine which package to install and > whether to download it is too complicated (and probably buggy). Also get > rid of calls to the newest_version script, allow gzip compression of > .spkg files, get rid of the "download again" part (why was it needed?). > > There is one important change in behaviour: when specifying a download > URL, it will always download the file, even if a corresponding spkg > exists locally. I think this is more in line with expectations.
Does this address the following issue? make sage -i http://url/of/package-1.2.spkg # an upgrade sage -b <test stuff> sage -f package-1.1 # should just go use, the current package IN spkg/ standard, right? Unpacked and it is empty/doesn't look like a tar archive ....Downloading.... Note that if one is using a development version of Sage with 1.1 while the last "stable" Sage has 1.0.2, you really end up in trouble. I don't understand why I can just drag and drop these spkgs from spkg/ standard and they seem fine, but using sage -i or even sage -f doesn't work. The next time this happens I'll be sure to post on it for reproducibility, if people think this is unintended behavior. -- 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
