Bug 1680400 - RapidJSON cmake and pkgconfig files reside in wrong place
Summary: RapidJSON cmake and pkgconfig files reside in wrong place
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rapidjson
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-24 17:37 UTC by Uwe L. Korn
Modified: 2020-07-30 18:13 UTC (History)
2 users (show)

Fixed In Version: rapidjson-1.1.0-14.el8
Clone Of:
Environment:
Last Closed: 2020-07-15 12:04:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Uwe L. Korn 2019-02-24 17:37:13 UTC
CMake configs are normally expected to reside under `/usr/lib{64}/cmake/RapidJSONCondig.cmake` and pkg-config files in `/usr/lib{64}/pkgconfig`. In the package spec these files are incorrectly moved to `_datadir`, this requires using custom paths when searching for RapidJSON in fedora.

Comment 1 Tom Hughes 2019-02-24 18:58:29 UTC
I think this has been done because the -devel package is noarch, though I'm not sure it should be. The packaging guidelines say that header only libraries should not be noarch, and the source rpm here isn't but the -devel subpackage isn't. I don't think that is how most header only libraries work - it's certainly not what I have normally done.

The pkg-config files are actually found as it, and I think the cmake ones might be if there were moved down into the Modules directory? I'm no cmake expert though.

Comment 2 Uwe L. Korn 2019-02-24 19:10:14 UTC
No, the CMake files should be at `/usr/lib{64}/cmake/RapidJSONConfig.cmake`, the Modules directory is only for the Find*.cmake files. But these are no longer required if the library provides a *Config.cmake.

As this packages behaves differently than all the others I have encountered in Fedora, I think it needs to adjusted. But this is the only header-only library I have to deal with and I'm not a Fedora user but solely someone that wants his users (from Apache Arrow) to be able to compile easily on Fedora; so I don't have any deep knowledge of Fedora packaging.

Comment 3 Ben Cotton 2019-08-13 17:10:26 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 4 Ben Cotton 2019-08-13 19:33:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 5 Fedora Update System 2020-07-15 11:56:03 UTC
FEDORA-EPEL-2020-f991149e2d has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f991149e2d

Comment 6 Fedora Update System 2020-07-16 01:45:53 UTC
FEDORA-EPEL-2020-f991149e2d has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f991149e2d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-07-30 18:13:15 UTC
FEDORA-EPEL-2020-f991149e2d has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.