Comment 9 for bug 2009495

The purpose of the /usr/lib/s390x-linux-gnu directory is to make libraries for multiple architectures co-installable on the same filesystem (multiarch).

If you're going to create a symlink from /usr/lib, and the package in question can't be co-installable because it also ships files in /usr/bin, and the programs that use it only access it via the /usr/lib/ path instead of the /usr/lib/s390x-linux-gnu path *anyway*, then it's useless to install the library in /usr/lib/s390x-linux-gnu at all. Instead of adding a link, you should *move* the file at build-time to the /usr/lib directory where it will be looked for.

Also, the filename ("preload") implies this isn't actually a shared library that programs will link against, but that they preload/dlopen it instead. For such cases, it's preferred that the library be shipped in a per-project subdirectory of /usr/lib. See libfakeroot for an example of this. This is not a blocker for SRU, just a comment on best-practices here.

The first issue, however, is an SRU reject for me. If we're going to touch this in an SRU, then we should do it the right way, not with extraneous extra symlinks.