5
On 11 February 2024 13:21:46 GMT, kcrisman <kcris...@gmail.com> wrote: > > >I believe I'm the person who introduced that long standing policy. It >was indeed motivated by a significant paying customer's requirement >to install Sage entirely from source, and without an external network. >I believe no such customers have supported the Sage project for about >a decade, so I'm very supportive of removing this policy. > > >However, at least in the not too distant past there have been situations >where the non-requirement of internet connectivity alleviated issues of >limited internet accessibility in a given locale, limited download speeds, >limited grid electricity, etc. This policy just as much affects those >situations, and perhaps some people who have installed Sage in such >environments (including Sage Days and other events) might want to weigh in >on that, and whether such situations still obtain (as I personally assume >they must certainly do). I figure three-letter agencies have people with >the skills to get around not using pip install, but if your downloads are >over a mobile network (or, for that matter, Project Kuiper or Starlink or >whatever), you might still want to download Sage - especially now that we >don't have binary installs "provided". > Sage 10.2 tarball is 1.3Gb, of which upstream/ subdirectory takes 80%. (for some reason there's also .git/ - something I don't get the reason for having at all, and .github/ - something that is not needed if you just want to build a full Sage). Of upstream/, ~50% is not needed on a typical Linux system, even if you go for a lazy approach of installing from the OS a dozen of most obvious packages, such as compilers, python3, pip, etc. On some linux systems you don't need anything in upstream at all. We can certainly provide a list of tarballs/wheels to download to create a complete upstream/, in case of a need to have a full offline install. Tools like wget can use such a list to get the files. Downloading in smaller chunks is more robust, by the way. And it reduces disk space requirements for the machine one uses, as well as space on the mirrors. Keeping a package as pip package or converting it to such a package further reduces the space required on mirrors, as well as the hassle of maintaining tarballs/wheels, etc. Dima -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/23FA599A-4596-4650-8E2F-BFC7C511E90B%40gmail.com.
