Bug 54462

Summary: pkg.m4: PKG_NOARCH_INSTALLDIR should use ${datarootdir} instead of ${datadir}
Product: pkg-config Reporter: Michał Górny <mgorny>
Component: srcAssignee: Tollef Fog Heen <tfheen>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Michał Górny 2012-09-03 20:46:14 UTC
-- Variable: datarootdir
     The root of the directory tree for read-only
     architecture-independent data files.

That is the directory in terms of which infodir, mandir and so on are declared. pkg-config should use that directory as well. The intent of it is that it still points to the system-wide 'share' subdirectory even if the particular package has redefined its ${datadir}.

Thus, PKG_NOARCH_INSTALLDIR should use ${datarootdir} to ensure the correct install location.
Comment 1 Dan Nicholson 2012-10-29 02:33:16 UTC
This seems like a good suggestion. However, the default path currently uses $datadir/pkgconfig. I don't think it would be wise to make the default install directory different than the default path. I'm closing assuming we don't want to change the default path right now.
Comment 2 Michał Górny 2012-10-29 08:26:28 UTC
(In reply to comment #1)
> This seems like a good suggestion. However, the default path currently uses
> $datadir/pkgconfig. I don't think it would be wise to make the default
> install directory different than the default path. I'm closing assuming we
> don't want to change the default path right now.

If you mean path in pkg-config, then it's irrelevant since in pkg-config $datadir is supposedly the same as $datarootdir. It can get important in other packages, however.

While at it, I'd also change the default path to use $datarootdir, to keep those in sync. It won't change a thing for pkg-config users but will help developers of other apps.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.