Hi Fabian, Quoting Fabian Grünbichler (2026-05-16 08:41:18) > rustc 1.95+ requires a version of wasm-libc that (build)-depends on > wasm-tools. > Since stable doesn't yet have that package, I am in need of a > backport ;)
Interesting challenge! [...] > Would you prefer me doing the backport (with minmimal changes if > required), or would you be willing to take the above three packages > on yourself? I will take care of the Rust team packages in any case. I have my hands full already, and plenty of exciting new packages to fill any excess time. So I would prefer to not do the backporting myself, but would prefer that you do it. If not too much extra work for you, then I would be quite interested in making these package as backportable as possible, so please consider filing bugreports for any changes to the unstable-targeted packages that you think might make ease your backporting work - i.e. consider "upstreaming" backporting changes to the main package where it makes sense. Most cool, but probably also most challenging, would be patches for covering both rand v0.8 and v0.10 - if someone figures out the pattern for doing that (and it isn't super complex to implement), then I am open to carrying and maintaining that type of patches in the main package, so that backporting require no patches for that class of issues. So what I mean is that I would prefer to not do the *initial* work if making backports work, nor the housekeeping of ensuring that the backports are in decent shape. But I don't mind added workload in my regular maintenance to ease backportability, if offered patched (which I then don't need to compose but need to maintain). Hope that makes sense, as is of some use, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
