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. I also think that would be easier to maintain than many spkg directories, one for each binary wheel. The only reason I know of for using separate directories is to allow a separate documentation file for each wheel. I don't think that documentation is really needed, as it could be replaced by boilerplate which references pypi. And, in practice, those individual documentation files would probably be constructed by copying and pasting from pypi anyway.
- Marc On Tuesday, August 6, 2024 at 8:17:34 PM UTC-5 Bagas Sanjaya wrote: > On Mon, Aug 05, 2024 at 08:28:12PM +0300, Georgi Guninski wrote: > > On Sun, Aug 4, 2024 at 9:03 PM Matthias Koeppe <matthia...@gmail.com> > wrote: > > > > > > > > In https://github.com/sagemath/sage/pull/38219 (needs review), I > propose the following mild policy change: > > > - as a third option, a "standard" package is allowed to be a Python > package that can be installed from platform-dependent (binary) wheels. In > this case, a "configure" option must be provided that disables the package. > > > > > > (Again this new option is motivated by avoiding the complexity of new > build infrastructure related to another language; in this case, Rust. See > the PR for two example Rust-based example packages; previous discussion: > https://groups.google.com/g/sage-devel/c/JiSryImYGe0/m/4B8z6F4AEwAJ) > > > > > > > I would recommend running antivirus just before `make install` and > > commercial supply chain backdoor scanner. Especially if there is no > > way to verify the integrity. > > In Windows, that's quite common for people to have antivirus installed. > But for people on Linux, they usually don't install one. > > -- > An old man doll... just what I always wanted! - Clara > -- 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/3a565bcf-7b90-4071-b620-b58eae41285fn%40googlegroups.com.
