Re: Bug#671979: (no subject)
On Thu, Jun 7, 2012 at 3:42 PM, Nikos Chantziaras rea...@hotmail.com wrote: If qmake in Debian doesn't depend on pkg-config, then that's to be expected. qmake is a build system that uses pkg-config. Most Qt applications don't make use of that functionality though. I'm not the Debian maintainer. I'm qtads upstream, chipping-in to point out that qmake should most probably depend on pkg-config :-) If qmake can function without pkg-config, that makes the dependency at most a Recommends. And if most Qt applications don't use the pkg-config functionality, then a Suggests seems most appropriate. (Cc to qt4-qmake package maintainers to get input on this point.) In either case, the original bug report would be correct that qtads should be Build-Depending on pkg-config. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADf0C45pfBNmWmfTX1_4AX=yojjhmjot+26d+pwmji5qf6j...@mail.gmail.com
Re: Bug#671979: (no subject)
On Jue 07 Jun 2012 23:26:55 Daniel Schepler escribió: On Thu, Jun 7, 2012 at 3:42 PM, Nikos Chantziaras rea...@hotmail.com wrote: If qmake in Debian doesn't depend on pkg-config, then that's to be expected. qmake is a build system that uses pkg-config. Most Qt applications don't make use of that functionality though. I'm not the Debian maintainer. I'm qtads upstream, chipping-in to point out that qmake should most probably depend on pkg-config :-) If qmake can function without pkg-config, that makes the dependency at most a Recommends. And if most Qt applications don't use the pkg-config functionality, then a Suggests seems most appropriate. (Cc to qt4-qmake package maintainers to get input on this point.) In either case, the original bug report would be correct that qtads should be Build-Depending on pkg-config. Most Qt applications do not need to use pkg-config. If an app needs an external library which ships a .pc file (libusb, for example), then the programmer needs to call pkg-config from within the .pro. So, it's the app that requires pkg-config and not qmake. For what I understand of the bug report, this is the case. Although part of Debian's Qt-KDE team, I don't usually hack in Qt itself (at least in it's packaging), but I think the team will agree that pkg-config should not be even a Suggest. If they don't... well, someone may change that ;-) Kinds regards, Lisandro. -- Theory and practice sometimes clash. And when that happens, theory loses. Every single time. Linus Benedict Torvalds. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: Bug#671979: (no subject)
On Thursday, June 07, 2012 08:15:41 PM Lisandro Damián Nicanor Pérez Meyer wrote: Most Qt applications do not need to use pkg-config. If an app needs an external library which ships a .pc file (libusb, for example), then the programmer needs to call pkg-config from within the .pro. So, it's the app that requires pkg-config and not qmake. For what I understand of the bug report, this is the case. Although part of Debian's Qt-KDE team, I don't usually hack in Qt itself (at least in it's packaging), but I think the team will agree that pkg-config should not be even a Suggest. If they don't... well, someone may change that ;-) Looking at qtads.pro, it contains: CONFIG += link_pkgconfig PKGCONFIG += sdl So it looks like there's an optional qmake feature to ease using pkg-config. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206072039.47006.dschep...@gmail.com
