Bug 254798 - pkgbase: -dev and -dev-lib32 packages both installing *.pc files.
Summary: pkgbase: -dev and -dev-lib32 packages both installing *.pc files.
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-pkgbase (Nobody)
URL:
Keywords: pkgbase
: 271853 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-04-05 16:15 UTC by beldin
Modified: 2023-09-16 18:49 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description beldin 2021-04-05 16:15:38 UTC 
The following package pairs:

liblzma-dev and liblzma-dev-lib32  (liblzma.pc)
libmagic-dev and libmagic-dev-lib32 (libmagic.pc)
runtime-dev and runtime-dev-lib32 (zlib.pc)
utilities-dev and utilities-dev-lib32 (libusb-0.1.pc, libusb-1.0.pc, libusb-2.0.pc)

Both packages reference the same .pc file and therefore cause a conflict if you attempt to install both. For example:

Checking integrity... done (1 conflicting)
  - FreeBSD-liblzma-dev-lib32-14.0.20210404 [base] conflicts with FreeBSD-liblzma-dev-14.snap20210404144818 [installed] on /usr/libdata/pkgconfig/liblzma.pc
Comment 1 Ed Maste freebsd_committer freebsd_triage 2022-11-16 19:26:38 UTC 
It looks like this is fixed in main, with .pc files being installed into /usr/libdata/pkgconfig/ or /usr/lib32/pkgconfig/ :

$ echo *-liblzma-dev-* | xargs -n 1 tar tvf | grep '.pc'
-r--r--r--  0 root   wheel     386 Oct 28 13:46 /usr/libdata/pkgconfig/liblzma.pc
-r--r--r--  0 root   wheel     388 Oct 28 13:46 /usr/lib32/pkgconfig/liblzma.pc
Comment 2 Mina Galić freebsd_triage 2023-06-12 13:20:35 UTC 
I think this fix should be MFC'd.
or is there anything it could break?
Comment 3 Mina Galić freebsd_triage 2023-06-12 13:21:31 UTC 
*** Bug 271853 has been marked as a duplicate of this bug. ***
Comment 4 Ed Maste freebsd_committer freebsd_triage 2023-06-12 13:35:19 UTC 
(In reply to Mina Galić from comment #2)
I do not know which commit fixed this.