The problem with the file name is that it can be wrong, so you'd have to be able to remove/overwrite previously-used names. Whereas the SHA1 is always correct and really is all that is needed to download the file from the Sage build scripts.
On Wednesday, August 26, 2015 at 10:42:44 PM UTC-4, Dan Drake wrote: > > On Saturday, August 8, 2015 at 12:22:18 PM UTC-7, Volker Braun wrote: >> >> In order to streamline updating third-party tarballs I've written a small >> web app where you can directly upload them. That way you don't need to host >> files yourself. Plus, the files can be retrieved by sha1 so with a little >> bit more scripting I won't always forget to manually copy them to the >> mirrors. Its a bit on the cutting-edge side (Python 3 aiohttp and Polymer) >> but should work on all current browsers, so its ready to beta-test: >> >> >> http://fileserver.sagemath.org:8080/ >> >> > Looks very nice. I uploaded the new sagetex tarball there. Everything > seems to work; my only suggestion is to somehow allow someone to download a > file with the original file name, instead of its SHA1. I made an issue on > your repo: https://github.com/vbraun/SageDevApp/issues/1. > > > -- 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/d/optout.
