On Thu, May 16, 2024 at 7:50 AM Faidon Liambotis <parav...@debian.org> wrote:
> Control: reassign -1 crun > Control: retitle -1 Ship the crun-wasm runtime > Control: severity -1 wishlist > Control: forwarded -1 https://github.com/containers/crun/issues/1468 > > On Sun, May 12, 2024 at 03:34:42PM +0300, Faidon Liambotis wrote: > > Perhaps it's worth bringing it up with both crun and podman upstreams, I > > don't think we're going to be the only distro dealing with this. (I can > > take care of that.) > > We have a little more clarity from Giuseppe. I'll work on shipping > crun-wasm on the next crun upload. (Still debating whether I should ship > it in a different package or not.) > > That's awesome, thanks for reaching out to upstream and getting input! As for what package should ship the symlink: I don't see a reason why you wouldn't have it in the same package. It could make sense if crun-wasm required additional dependencies that wouldn't be required otherwise. Or if its presence somehow degraded / limited the wasm functionality. It might make sense to ship the symlink in the crun-package and have a Provides: crun-wasm relationship. -- regards, Reinhard
