make default perl install path respect CMAKE_INSTALL_PREFIX#2054
make default perl install path respect CMAKE_INSTALL_PREFIX#2054evgenyz merged 3 commits intoOpenSCAP:maint-1.3from
Conversation
Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
|
Hey! Sorry about it taking so long to review. I'm a bit confused with minor versions. Here is what I have in Fedora: Can't see any minor-version directories. I wonder, how it will actually function? |
|
What's under |
|
|
I was hoping this would not require distro-specific hacks... Anyway, using some perl path returned by |
|
Sorry, I meant using that ^^ by itself. Which means a bit more cmake foo is required, along with trusting the paths shown in the cmake docs. I should be able to push another commit shortly. |
|
After checking a few installs it looks like a free-for-all under the perl install paths with multiple/nested directory trees for what are essentially the same file types so I would expect Fedora to be tolerant enough to accept the versioned subdirectories I see on pretty much any system, starting with the cmake perl paths: The current install paths in my top commit can certainly be improved, hopefully after dinner. With the vendor paths adjusted for prefix I get this: |
* also display both vendor/non-vendor system paths in linux envs Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
|
If not specified, cmake default install prefix on Linux/mac is Oh yeah, can you run this on fedora and post the perl paths here? Thanks! |
I'm not sure what you want me to post exactly, but if you mean output of this: then you can check it out yourself for every distro we gate against in CI logs (e.g. https://github.com/OpenSCAP/openscap/actions/runs/7216196068/job/19661940675?pr=2054#step:5:249). |
|
Doh! It's so much fun when everyone gets their own PATHs. |
|
Hmm, after still more thought, I added a check for default instead. I think that's about it (unless you want a custom default or other changes). Thanks! |
Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
|
Great. Thank you! |
|
The test failure is not relevant to the changes. |
|
Hello, For example having i686 package installed next to the x86_64 package would collide in the openscap_pm.pm x86_64: Yes perl might probably live with just 3 files, but the RPM (and possibly other package managers for other distros) won't be happy. Unless we package openscap_pm.pm as noarch and openscap_pm.so as arched, but in my opinion that would be overkill. Example reference packages using DynaLoader same as openscap: perl-Digest-SHA-6.04-501.fc39.x86_64 having: perl-GD-2.78-3.fc39.x86_64 having: perl-Glib-1.3293-13.fc39.x86_64 having: Best regards |
Rebased as requested, same name as the original PR (#1999) (sorry about any confusion).