As far as I can tell, that is quite different from what I was suggesting. It involves a separate package directory for each binary wheel, not one directory for many binary wheels which would all get installed together at the end of the build process in one big pip run.
However, I was naively looking at this from the point of view of someone maintaining a port of Sage to a single platform, which also happens to allow a single binary wheel to work for multiple versions of the OS. Looking at that linked file reveals that the linux situation is infinitely more complex. The version "pinning" apparently must be done separately for each release of each distro. Probably there is no way to tame that maintenance headache. Possibly Sage could hope to "delegate" the job of deciding which version of each binary wheel is optimal for each release of each distro to the package maintainer(s) for that distro and to copy the data for those checksum.ini files from some known location within each distro. However, I don't see how that will work for the majority of distros given that they are not close to supporting the current version of Sage. I don't know if this scheme will end up being simpler than installing Rust in the Sage build directory (which involves very little more than downloading and running rustup.sh). I hope it will. - Marc On Friday, August 9, 2024 at 8:54:48 AM UTC-5 Nathan Dunfield wrote: > On Thursday, August 8, 2024 at 7:57:12 AM UTC-5 Marc Culler wrote: > > I think it would be possible to use a single spkg for all of the > additional binary wheels, where the main content of that spkg is a > requirements.txt file listing versions and hashes. > > > Yes, that is approach Matthias implemented in the accompanying PR ( > https://github.com/sagemath/sage/pull/38219), though the data is in the > "checksums.ini" file. For example: > > > https://github.com/sagemath/sage/blob/fdc545367173f836890b9cddbce0d7c032b10d2b/build/pkgs/rpds_py/checksums.ini > > > Best, > > Nathan > -- 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/329f7a4e-d23f-4e62-903c-80f4e26d5f73n%40googlegroups.com.
