Summary: | ldconfig runs when its not needed | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Dylan Carlson (RETIRED) <absinthe> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | mr_bones_ |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dylan Carlson (RETIRED)
2003-04-17 01:59:55 UTC
The reason it runs ldconfig so many times is mostly for safety. The problem with doing as is suggested here is that env_update would have to be informed of all information used for merging and unmerging packages. env_update is completely seperate from the merge process and updates the files used when calculating ldconfig's path info. It's a complexity and safety issue... This might get cleaned up more in the distant future, but for the time being, it won't change. |