On 2025-05-07 13:28:13, Tony Luo wrote: > Thank you for the detailed response. I actually tried to patch the existing > release with the generated ".patch" file from the GitHub commit URL prior > to just bumping the source. A naive attempt fails (as expected) since there > is quite a large set of changes between the commit and the current packaged > release.
It looks like the only conflicts are in the files under "Tst", which I assume are test files. If you edit those hunks out of the patch the rest should apply cleanly on top of singular-4.4.1. I did a quick build & test and nothing bad happened. > Regarding the use of autotools, would generating ./configure during the > build with a spkg-src script be acceptable here or would you still > recommend waiting until the next Singular release? It's acceptable and we do it for a few other packages. The return on investment would be comparatively low in this case because the changes are already upstream, unlike (say) when we rewrite an entire dead package's build system. But if you want to do the work and if you can get someone to review it, sure. -- 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 visit https://groups.google.com/d/msgid/sage-devel/aBwL8OOWEP9KcepQ%40mertle.
