Skip to content

Conversation

@eximius313
Copy link

Fixes #309

The previous logic for fixing RPATHs in shared libraries (lib*_plugin.so) only triggered if the path contained /home. This caused build paths to leak into the final package when building in other environments (e.g., /mnt/... in WSL, /root in Docker, or /opt in CI runners).

This commit changes the condition to check for any absolute path (starting with /) that isn't already set to $ORIGIN.

…ectories

The previous logic for fixing RPATHs in shared libraries (`lib*_plugin.so`) only triggered if the path contained `/home`.
This caused build paths to leak into the final package when building in other environments (e.g., `/mnt/...` in WSL, `/root` in Docker, or `/opt` in CI runners).

This commit changes the condition to check for any absolute path (starting with `/`) that isn't already set to `$ORIGIN`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[RPM] RPATH sanitization logic is too restrictive (fails for builds outside '/home')

1 participant