Drop automatic inclusion of .pc file for baselibs. #1002
Conversation
Fixes openSUSE#724. Avoid default inclusion of pkgconfig files in automatically generated baselibs configured biarch packages. This avoids the "have choice" issue seen with `BuildRequires: pkgconfig(FOO)` type dependencies on OBS for any dependents of a biarch FOO-devel package. It is wrong to ask every project supporting biarch devel packages to configure project macros to disfavour one pkgconfig based dependency in favour of another. Packager may at their wish explicitly include the pkgconfig file in the biarch package explicitly by appropriately configure the associated baselibs.conf file, but as a default, this should be hardly ever required.
|
Ping? |
|
See https://bugzilla.suse.com/show_bug.cgi?id=1172563, which asked for adding the .pc files. |
|
Thanks for the reference. Looks to me like the missing piece of the puzzle — correct RPM autoprovides for baselibs — has been missing for a while. From reading that bug report, it seems everyone pretty much agrees that packaging .pc files for the baselibs without first correcting the autoprovs is a mistake that is haphazardly worked around in Factory but needs similar hackish workarounds for every project using these biarch libs. I would still suggest skipping automatic inclusion of these .pc files. |
|
Off the top of my head, the other option would be to turn off |
|
If OBS could handle Prefer using RegEx, one could do:
|
That would also have to be done for every project, wouldn't it? |
yes (let alone that OBS would actually need to support it first); but we only have a list of like 3 supported distros- so adding this in 3 places would not be really hard |
3 participants
Fixes #724.
Avoid default inclusion of pkgconfig files in automatically generated baselibs configured biarch packages. This avoids the "have choice" issue seen with
BuildRequires: pkgconfig(FOO)type dependencies on OBS for any dependents of a biarch FOO-devel package. It is wrong to ask every project supporting biarch devel packages to configure project macros to disfavour one pkgconfig based dependency in favour of another.Packager may at their wish explicitly include the pkgconfig file in the biarch package explicitly by appropriately configure the associated baselibs.conf file, but as a default, this should be hardly ever required.