I'm not sure this is a good idea. Even if one is using autoconf, the value of libdir comes from the user, or a default like /usr/local/lib
In short, I think a better policy is to follow the one from libdir itself; it's a user config option, /usr/local/lib is a good default, and it's up to the user (or packager) to set it as they like and make sure pkg-config is itself configured to look there if they want it to be picked up. These defaults work fine for less sophisticated users, and trying to be more clever gets in the way of people trying to do parallel installs and so on. Consider: on debian `pkg-config --variable=libdir pkg-config` would return /usr/lib which is certainly *not* where user-built source should install itself. On the other hand, a debian package should put its .pc files in /usr/lib/pkg-config regardless of whether `which pkg-config` is from debian, or some customized version in /usr/local or /opt. FWIW, -r -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
