On Sunday, April 17, 2016 at 2:14:09 AM UTC+1, kcrisman wrote: > > > >> >>> (1) Providing a source tarball from which one can build Sage without >>> internet access is a basic requirement from a company that provides >>> some funding for Sage development over the years. We don't >>> contractually have to do it, but I think it is a good to be able to do >>> so. (2) It is also helpful when we have Sage days workshops at places >>> with crappy internet (frequent), since at least everybody can build >>> Sage locally from a single tarball. >>> >> >> PS. in my eyes, my proposal would bring Sage closer to "normal >> open-source development >> practices" that you were arguing for recently. No normal project I know >> creates >> megamegatarball of everything; reducing these would be a step in the >> right direction. >> >>> >>> > Remind me again how this helps with (2)? But more seriously, is there a > way to have the "normal" distribution be pip or whatever but have a > scriptable way to create a tarball for everything that is just not the > default one people are pointed to? I assume yes. > here is one I found http://doc.devpi.net/latest/quickstart-pypimirror.html
it will create a pypi cache that can be served locally. Then, I saw a link saying that a complete pypi mirror is "just" 120GB. Even if this is 5 times too optimistic, it would still fit on a portable 1TB or so disk you can take with you. Perhaps a single tarball was important to have 10 years ago, nowadays it's really not something so important... -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
