Description of problem: To simplify the use of the library and checking in tools like rpm and cmake it would be beneficial to have a pkg-config file in the -devel package Version-Release number of selected component (if applicable): libunistring-0.9.10-14 How reproducible: always Steps to Reproduce: 1.cat /usr/lib64/pkgconfig/libunistring.pc 2. 3. Actual results: no such file Expected results: Perhaps something like this: prefix=/usr exec_prefix=/usr includedir=/usr/include libdir=/usr/lib64 Name: GNU libunistring Description: GNU libunistring library implementing Unicode string types in three flavours URL: https://www.gnu.org/software/libunistring/ Version: 0.9.10 Cflags: -I${includedir} Libs: -L${libdir} -lunistring Additional info:
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
I think it would be good to suggest this to upstream https://savannah.gnu.org/bugs/?group=libunistring Though I suppose a .pc file could be carried in Fedora in the meantime.
FYI, the previous discussion at https://lists.gnu.org/archive/html/bug-libunistring/2018-02/msg00000.html As for having a .pc file in downstream only, I don't see much benefit as applications wouldn't be able to assume its presence.