On Mon, Feb 12, 2024 at 11:52 PM Matthias Koeppe <matthiaskoe...@gmail.com> wrote: > > I'll now offer: > > Opinion 1. Nobody needs to care in the slightest what the size of that > release tarball is.
Not quite true. E.g. the mirrors are not of infinite size, e.g. some projects (symengine is an example, IIRC) on PyPI get constrained that way. > > In any use cases with internet connectivity, people will be better off by > just cloning the git repo, not use the release tarball. > > If there are relevant use cases without internet connectivity (I have no > opinion to offer on this), then the release tarball has exactly the right > contents. This won't be true any more if we allow standard packages to be pip packages. > > Proposed action items: > A. Change https://github.com/sagemath/sage/blob/develop/README.md so that > "git clone" is described as the primary way to obtain the Sage sources. That > the big release tarball is available can be a footnote in the Installation > Guide > (https://deploy-livedoc--sagemath.netlify.app/html/en/installation/source#installation-steps) > for the limited no-internet connectivity use case. > > B. Likewise, get rid of all of these "Download Sage source code" pages > (https://www.sagemath.org/download-source.html, > https://www.sagemath.org/download-latest.html), mirror selection, etc. from > the Sage website. > > > On Sunday, February 11, 2024 at 11:23:42 AM UTC-8 Dima Pasechnik wrote: >> >> Currently the standard packages cannot be pip packages, i.e. we must, in >> effect, vendor them. This entails an extra effort which is often not needed, >> in particular as we patch only very few Python packages. >> Pip packages are on the other hand installed straight from PyPI. >> >> Good examples of standard packages which can become pip ones are tox, pytest >> (not yet standard). >> >> >> The other difference is that by default these packages are not included in >> the Sage releases source tarball. >> >> Rather than adding them there I propose to split the upstream/* part of the >> tarball into something optional - which is represented by a list of files to >> download, and which is just not needed if you build while connected to the >> internet. >> >> This is a huge saving on the tarball size: with upstream/* in, Sage 10.2 >> tarball is 1.3Gb, and without it is smaller than 0.25Gb. >> >> Note that as William writes, the desire to have Sage buildable without an >> internet connection was a requirement by a past Sage funder, gone about 10 >> years ago. Thus there's no longer an obligation to have this option. >> I am not aware of a similar to Sage which provides tarballs allowing for an >> offline build. >> >> Thus, I would like to call a vote on these two topics: >> >> 1) allow standard packages to be pip packages >> >> 2) drop the contents of upstream/ from the Sage source tarballs. >> >> >> --- >> 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/f926e074-9803-4335-b128-29398c460b0en%40googlegroups.com. -- 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/CAAWYfq0QmtZ5hY39%3DSmfmdtP97wqnQDBstRq7iAd_EwVJHHxXw%40mail.gmail.com.
