[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

pkg-config issues


I've just started packaging some library which provides .pc file for
pkg-config. So I was wonder where to put this file and if my -dev package 
should depend on pkg-config.

As usual I started looking how it is done in other libraries and
unfortunatelly this didn't lead me to clear answer.
Seems that policy doesn't describe it either.

Problem a:

Where .pc file should be put?
Let's say I've got libXXX<soname> and libXXX-dev packages.

I suppose that I should put it in libXXX-dev package, but I found some
packages which contain this file in libXXX<soname>.

Problem b:

Should my package depend on pkg-config?
I thought yes, but many packages didn't do that.

Some conclusions.

Should I fill bugreports against packages which contain either 
problem a or b (or even both)?

Maybe policy should mention about correct way of handling such files?
Maybe linda/lintian should warn if these problems occur?


      _      Bartosz Fenski | mailto:fenio@o2.pl | pgp:0x13fefc40 | IRC:fEnIo
    _|_|_     32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska
    (0 0)          phone:+48602383548 | Slackware - the weakest link
ooO--(_)--Ooo  http://skawina.eu.org | JID:fenio@jabber.org | RLU:172001

Attachment: signature.asc
Description: Digital signature

Reply to: