Creation of pkgconfig file for libraries that do not ship one

[Guido Aulisi]

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.

Thank you
Guido

FAS: tartina

[0]: https://bugzilla.redhat.com/show_bug.cgi?id=1809043

[Neal Gompa]

On Mon, Mar 2, 2020 at 6:03 AM Guido Aulisi <guido.aulisi(a)gmail.com&gt; 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.
>
>  Thank you
>  Guido
>
>  FAS: tartina
>
>  [0]: https://bugzilla.redhat.com/show_bug.cgi?id=1809043 
In general, if you want to do this, you should contribute it upstream.
Those files are only useful if people can actually use them, and
generally they are only used if upstream has them.



-- 
真実はいつも一つ！/ Always, there's only one truth!

[Daniel P. Berrangé]

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 :|