[1021479771] Upstream Reporter: Дилян Палаузов
Upstream issue status: Closed
Upstream description:

Using the meson build system, calling ninja install prints on my system:

[0/1] Installing files.
Installing conmon to /usr/local/libexec/podman

Using the make build system, calling make install prints:

install  -D -m 755 bin/conmon /usr/local/bin/conmon
make -C tools
make[1]: Entering directory '/src/containers/conmon-2.0.30/tools'
make[1]: Leaving directory '/src/containers/conmon-2.0.30/tools'
make -C docs
make[1]: Entering directory '/src/containers/conmon-2.0.30/docs'
../tools/build/go-md2man -in conmon.8.md -out conmon.8
make[1]: Leaving directory '/src/containers/conmon-2.0.30/docs'
make -C docs install
make[1]: Entering directory '/src/containers/conmon-2.0.30/docs'
install -d //usr/local/share/man/man8
install -m 0644 conmon*.8 //usr/local/share/man/man8
make[1]: Leaving directory '/src/containers/conmon-2.0.30/docs'

So the one build system install under /usr/local/bin/conmon, the other build system installs under /usr/local/libexec/podman . This makes no sense. I see no point to install conmon under /usr/local/libexec, when it will be called by cri-o.