On Mon, Mar 02, 2020 at 12:03:01PM +0100, Guido Aulisi wrote: > Hi, > can we create a pkgconfig file for libraries that do not ship one? > I did not find anything about that in our packaging policy. > > A bug was filed [0] about a missing pkgconfig file for zita-convolver > library and I'm thinking og creating the missing pkgconfig file > myself. I can certainly understand the desire to have a pkgconfig file for every library that exists. With my app developer hat though on I'd encourage you *not* to add this in downstream Fedora packaging, as this effectively forks the project from the POV. Any application which depends on use of the pkg-config file will now only build in Fedora, or other distros which have also added the non-upstream pkg-config file. If they keep fallback logic for the non-pkg-config case, this makes their life even harder as now they have 2 ways to detect dependancies to maintain & hope they both have the same semantics. Thus I'd encourage you to take the request for a pkg-config file straight to the upstream project. Most projects are receptive to this kind of thing, especially if you're providing the patch. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
