On Tue, Apr 10, 2007 at 08:25:13AM -0700, Matthew Dillon wrote: > The only worry here is that having the paths might hide breakage > elsewhere in the pkgsrc system. But I don't think it would be a > big issue.
The reverse is the problem. Using ldconfig for this essentially breaks the ability to have multiple incompatible versions of the same DSO in the filesystem. Consider for example a library linked against libarchive -- you can't ensure easily that it gets a major version bump as well. This is fine as long as all programs e.g. in /usr and /usr/pkg agree on the version they need and want. It doesn't stop me from installing a separate version in /usr/local for the programs I can't recompile easily etc. rpath allows me precise control of what library I end up with -- ldconfig is much coarser at that. Like I said, ldconfig should pretty much die except for the few situations where it is useful. But most of those are system specific and *don't* make proper defaults. Joerg
