I am still digging exec_prefix peculiarity (vs prefix which is compile time , exec_prefix is install time, that is all I grasped as of now)

from https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Installation-Directory-Variables.html the exec_prefix should not get expanded until install step

for one PIDFILE also keep ${prefix} unexpanded
but this is somehow managed during the package build as at least debian ends up expanding the ${prefix}
though did not stumbled on the when it does so (and either when exec_prefix should be expanded per gnu rules)

also I did not managed to make sense out of "A corollary is that you should not use these variables except in makefiles. " about sbindir , bindir, etc ;
vs later in the doc:
"Similarly, you should not rely on AC_CONFIG_FILES to replace bindir and friends in your shell scripts and other files; instead, let make manage their replacement. "
from:
https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Installation-Directory-Variables.html

I find that "do not use them in other places than makefile" and "in other files than makefiles , you should use make code to manage the replacement" conflicts.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.5
rhbz: => 0

Patch should fix the issue with replacing bindir in systemd service files
0001-test.patch

Can you send the patch to sssd-devel? Or would you like to see some test results first?

owner: somebody => lslebodn

Fields changed

patch: 0 => 1
status: new => assigned

• master: a203f4a

• sssd-1-11: 1f4df57

resolution: => fixed
status: assigned => closed

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3335

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.