Bug 91391 - poppler-data's Makefile should install pkgconfig files to arch-dependent location
Summary: poppler-data's Makefile should install pkgconfig files to arch-dependent loca...
Status: RESOLVED NOTABUG
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-19 06:29 UTC by Kylie McClain
Modified: 2015-11-21 21:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
[PATCH] Makefile: install pkgconfig files to arch-dependent location (1.21 KB, text/plain)
2015-07-19 06:29 UTC, Kylie McClain
Details

Description Kylie McClain 2015-07-19 06:29:19 UTC
Created attachment 117241 [details]
[PATCH] Makefile: install pkgconfig files to arch-dependent location

pkgconfig files should be installed to arch-specific locations almost always,
because otherwise it can result in having a package installed for two different
architecture on one system (i686/x86_64, for example) and the files end up
clobbering each other. The attached patch changes the Makefile to install it to
$(libdir)/pkgconfig instead.
Comment 1 Albert Astals Cid 2015-07-19 11:16:17 UTC
Can you please explain why poppler *data* should be *architecture* dependent?
Comment 2 Kylie McClain 2015-07-19 16:39:49 UTC
It's purely a QA thing. It prevents files from two different architectures on one filesystem from overwriting each other when one is installed on a system with poppler-data already installed for one architecture.

The case for this is Exherbo's multiarch, which we are trying to ban installation to /usr/share/pkgconfig with, since it tends to be architecture dependent.
Comment 3 Albert Astals Cid 2015-07-19 16:53:53 UTC
I'd argue your distro is doing it wrong if you have arch-dependent packages for  poppler-data.


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.