On Thursday, August 15, 2024 at 4:11:50 AM UTC+9 Matthias Koeppe wrote: On the other hand, the "sage-10.4.tar.gz" tarball that is built by the Release Manager and put on the Sage mirrors (as well as the "sage-10.4.tar.gz" tarball that is built using the same procedure and put on GitHub Releases - https://github.com/sagemath/sage/releases/tag/10.4) does contain an upstream/ directory that is populated with the upstream tarballs/wheel files of all standard normal/wheel packages.
Do you mean this https://github.com/sagemath/sage/archive/refs/tags/10.4.tar.gz ? This one also does not have "upstream/" directory. The installation guide does not tell me where I can download sage-10.4.tar.gz that contains upstream/ directory. Where is it? Sigh... With the branch of https://github.com/sagemath/sage/pull/38219, also the new binary wheel files (such as rpds_py-0.18.1-cp310-cp310-macosx_11_0_arm64.whl and rpds_py-0.18.1-cp310-cp310-musllinux_1_2_i686.whl) will appear in this directory. Would all they be included in (upstream/ directory of) the release tarball say sage-10.5.tar.gz? Then I fear that platform-dependent standard package would be a sure way to bloat the release tarballs. A user on a specific platform is forced to download many unnecessary wheel files via sage-10.x.tar.gz. To avoid this, we are forced to provide different tarballs for different platforms. I am back to my original question... -- 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/33734e85-276b-4ee7-bb5a-b4312a1a9320n%40googlegroups.com.
