On Sun, Dec 01, 2024 at 12:42:14PM +0100, Paul Gevers wrote: > Hi Julian, > > On 10/14/24 20:58, Julian Gilbey wrote: > > (3) Compatibility issues: As discussed, the version of emscripten is > > closely tied to the versions of LLVM and binaryen, and not necessarily > > in a reliable way. I suggest that we add some sort of script in > > debian/, that is called from both uscan (so referenced in the d/watch > > file) and from an early step in d/rules (eg execute_after_dh_testdir) > > that looks at the upstream version number and checks that it's > > compatible with the versions of LLVM and binaryen listed in d/control. > > So we would hard-code into this script that emscripten 3.1.62, say, is > > compatible with llvm-19 and binaryen 122; if the upstream version > > isn't listed, then it will exit with a warning message and error, > > pointing to the GitHub discussions. This will help to ensure that > > future developers don't unknowingly update the package without > > checking for compatibility. > > More than one month has passed, and I'm pondering how to move forward. > Should we take your changes and apply them on an older version of emscripten > that works with the (highest) llvm we have in Debian at this moment? > > Any better ideas? > > Paul
Hi Paul, That might well work, but beware that some of my changes were needed because the emscripten internals changed, so an older version of emscripten might require some of those changes to be rolled back. Also, someone pointed out that we have to make sure binaryen is also at a compatible version. So frustrating that upstream doesn't offer a version that coordinates with released versions of llvm and binaryen. Best wishes, Julian
