There are a few ways to mitigate the library issue on Linux:

1. Package the libraries with your executable and use a loader shell script that sets LD_LIBRARY_PATH accordingly. This is the method used by Ren'Py.
2. Speaking of: if your game is in Python, you can use Nuitka or PyInstaller to make a stand-alone directory you can zip up and distribute.
3. Failing that, use a language that builds all it can statically into the executable. Go, D and Nim are like that. Edit: I think so is Rust.
4. Actually you can do that with C / C++ too, but it's tricky and some distributions (*cough* Debian *cough*) hate static libraries.
5. Worst case, use a slightly older Linux to build, and let players know they're going to need SDL2 or whatever installed. They're probably going to have it anyway, and it's no different from telling Windows users to install the latest DirectX.

So, we don't exactly have rules about it because there aren't any, but maybe some of these ideas will help you.

I see no reason to tell people what packages they need to install. They, as the users of their respective system, ought to know that better than I do.

I also haven’t had many problems with distributing basic Linux executables that load dynamic libraries. By far the worst thing to deal with is glibc’s versioned symbols, but there are ways around it.