On Tue, Aug 25, Aaron Puchert wrote:
Am 25.08.20 um 22:54 schrieb Jan Engelhardt:
%install ... if ! test -e %buildroot/%bindir/ccc-analyzer; then ln -s %_libexecdir/ccc-analyzer %buildroot/%bindir/ccc-analyzer fi ...
It does not hurts to have a symlink too much.
Hmm, but isn't the idea behind /usr/libexec to have the executables not in $PATH, because they are not meant to be invoked by users?
Correct, having them in bin and libexec doesn't make much sense. I would check if /usr/libexec exists, if yes, use it, else /usr/bin. Thorsten
These two are only used internally by scan-build, which looks for them first in /usr/libexec, then /usr/bin:
# Determine the location of ccc-analyzer. my $AbsRealBin = Cwd::realpath($RealBin); my $Cmd = "$AbsRealBin/../libexec/ccc-analyzer"; # ... if (!defined $Cmd || ! -e $Cmd) { $Cmd = "$AbsRealBin/ccc-analyzer"; DieDiag("'ccc-analyzer' does not exist at '$Cmd'\n") if(! -e $Cmd); } # ...
So if it's in /usr/libexec, it doesn't need to be in /usr/bin. But for older distros (currently everything != Tumbleweed) I want to keep them in /usr/bin since /usr/libexec doesn't exist and %{_libexecdir} == /usr/lib, where the script doesn't look.
Best regards, Aaron -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org