On Monday 16 January 2012 12:00:59 pm Bruce Dubbs wrote:
> Baho Utot wrote:
> > On Monday 16 January 2012 08:50:34 am Darrell Anderson wrote:
> >>> As a packager you should move it to
> >>> /usr/lib/pkgconfig.  That's where all the
> >>> pkcconfig files should be anyway.
> >>
> >> Are you saying that when I create Trinity packages to install to
> >> /opt/trinity, I should still install pkgconfig files to
> >> /usr/lib/pkgconfig?
> >
> > Yes that is correct. pkg-config looks there by default as that is how the
> > default configuruation is.  I ove all of the ones that are not installed
> > there.  Less toruble that way.
>
> There is nothing wrong with putting a group of .pc files in another
> location, say, /opt/trinity/lib/pkgconfig.  You only have to set one
> environment variable:
>
> PKG_CONFIG_PATH=/opt/trinity/lib/pkgconfig:/opt/xorg/lib/pkgconfig
>
> To me, just setting a variable once is far less trouble than moving
> files for every package.  It also supports the situation where you may
> want to have trinity-3.5.13 and trinity-devel on the same system.
>
> Users who don't build from source don't have to worry about it at all.
>
>    -- Bruce

True

If one either moves the .pc file to /usr/lib/pkgconfig or symlinks in tha 
package then I don't have to mess around define vars. or things of the 
nature.  "It just works"