Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#72378 - [xtrans][xorg-util-macros] .pc files maybe needs install in architecture agnostic path
Attached to Project:
Arch Linux
Opened by Gustavo Alvarez (sl1pkn07) - Sunday, 10 October 2021, 02:02 GMT
Last edited by David Thurstenson (thurstylark) - Saturday, 12 March 2022, 20:37 GMT
Opened by Gustavo Alvarez (sl1pkn07) - Sunday, 10 October 2021, 02:02 GMT
Last edited by David Thurstenson (thurstylark) - Saturday, 12 March 2022, 20:37 GMT
|
DetailsHi.
the .pc files in both packages install the .pc files in /usr/lib due is a headers only/set defines packages, this .pc files maybe set installed in archtitecture agnostic path, like /usr/share/pkgconfig in the packagebuidls have this lines added 13/11y ago https://github.com/archlinux/svntogit-packages/blob/packages/xorg-util-macros/trunk/PKGBUILD#L27-L28 https://github.com/archlinux/svntogit-packages/blob/packages/xtrans/trunk/PKGBUILD#L29-L30 maybe need remove and leave untouched the upstream behavior greetings |
This task depends upon
1108
andyrtr@workstation64:[/tmp/luit/trunk]$ find /usr/share/pkgconfig/ | wc -l
67
Afaik there's no strict rule from FHS but in the recent years files moved over /usr/lib.
greetings
PKG_CONFIG="i686-pc-linux-gnu-pkg-config" is it used in any arch packages at the moment? because PKG_CONFIG_PATH="/usr/lib32/pkgconfig" is how arch package guidelines dict https://wiki.archlinux.org/title/32-bit_package_guidelines
greetings
then something happen in offical multilib repository. all lib32 packages i see in it uses the wiki lib32 package guideline convention. so, what i need to do?
open a other issue?
greetings