That's a really interesting question. I created some small games with Löve and really loved it. However I always found the whole packaging/distribution/deployment a bit of a problematic topic.

If you don't just want to distribute a .love file (e.g. you do not want your user to get the Löve runtime themselves) this was basically unsupported and you had to come up with your own solutions..

I still think if the Löve community could improve this part it would help the most.

I'll throw in my 3c, it was 2016 and I've been trying to create a fully static x86-64 Linux binary, to hopefully avoid all the problems with DLL hell (as Löve links to an awful lot of stuff, and judging by the .so numbers it was unlikely to work in a year or two). TL;DR I've spent more time fighting the linker than writing the actual games ;)

I didn't want to rely on whatever-version-of-löve-this-distro-has-packaged because Löve at the time would break API compat quite frivolously. You can probably use an AppImage these days but I think this goes against the intent and spirit of Löve. It should be trivial to build entirely self-contained binaries; and in case of Windows/Mac, it was indeed the case (modulo code signing).