Do not run ldconfig in post install nonchroot #131
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ister and swupd run ldconfig after an install redundantly. We want to
have ister default to letting swupd run its post install triggers, or
having a user run these manually in the same way that swupd would with
their post script, rather than replicating part of them itself. Running
ldconfig differently in both instances has the side-effect of removing
broken library symlinks from an install.
Signed-off-by: George T Kramer george.t.kramer@intel.com