scripts: add replacements scripts for /sbin/ldconfig calls in glibc-common

[keszybz]

The scriptlet in glibc adds a dependency on bash to glibc-common, which
is required by glibc, so effectively the whole world depends on bash.
I want to rewrite the script in lua to drop this dependency.

Quoting https://bugzilla.redhat.com/show_bug.cgi?id=2018913#c34:

warning: SCC #1: 5 members (5 external dependencies)
warning: 	glibc-2.35-2.fc37.x86_64
warning: 		-> glibc-minimal-langpack-2.35-2.fc37.x86_64
warning: 		-> glibc-common-2.35-2.fc37.x86_64
warning: 	ncurses-libs-6.2-9.20210508.fc36.x86_64
warning: 		-> glibc-2.35-2.fc37.x86_64
warning: 	bash-5.1.16-2.fc36.x86_64
warning: 		-> ncurses-libs-6.2-9.20210508.fc36.x86_64
warning: 		-> glibc-2.35-2.fc37.x86_64
warning: 	glibc-common-2.35-2.fc37.x86_64
warning: 		-> glibc-2.35-2.fc37.x86_64
warning: 		-> bash-5.1.16-2.fc36.x86_64
warning: 	glibc-minimal-langpack-2.35-2.fc37.x86_64
warning: 		-> glibc-common-2.35-2.fc37.x86_64
warning: 		-> glibc-2.35-2.fc37.x86_64

If we look into SCC #1, bash obviously requires glibc because it links
to it. The loop is created by glibc → glibc-common → bash, because
glibc-common has %transfiletriggerin and %transfiletriggerpostun using
bash to call /sbin/ldconfig.

[openshift-ci]

Hi @keszybz. Thanks for your PR.

I'm waiting for a coreos member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[lucab]

/ok-to-test

[lucab]

Thanks for the proactive PR! I did read through the BZ and I think this makes sense to do.
The actual glibc-common change is at https://src.fedoraproject.org/rpms/glibc/pull-request/54, and I think it would be good to leave a breadcrumb to that in the code.

I'd leave some space for @cgwalters and @jlebon to have a look at the thread, as this is a place usually full of surprises.

[jlebon]

Yes, thanks a lot for opening this upfront! Agreed re. adding a link to the dist-git PR (and the RHBZ too would be good).

The patch itself LGTM otherwise.

[keszybz]

Well, I had to push one of the pull requests first. This one got the short straw ;)

I added the links and expanded the commit message bit.

[jlebon]

Thanks! I took the liberty of including the links in a comment as well to make it easier to keep track of this growing pile of hacksworkarounds.