Package: libmodplug-dev Version: 1:0.8.8.4-1 Attempting to link a program, using pkg-config's advice, against both libsndfile1 and libmodplug1 results in pain. IMO, libmodplug's pkg-config metadata is suspect...
$ dpkg -S sndfile.h | grep e.h$ libmodplug-dev: /usr/include/libmodplug/sndfile.h libsndfile1-dev: /usr/include/sndfile.h $ pkg-config --cflags libmodplug -I/usr/include/libmodplug Normally (having looked at the source of all the packages that link against libmodplug) applications #include <libmodplug/whatever.h> so there's no reason for pkg-config to suggest using -I/usr/include/libmodplug when the default /usr/include path is enough to do the job. Not every package follows that practice, cmus cynthiune.app, and xmms2 don't. Still, I'd argue it's the right thing to do, and the current pkg-config metadata is bogus. -- Jamie Heilman http://audible.transient.net/~jamie/ "You came all this way, without saying squat, and now you're trying to tell me a '56 Chevy can beat a '47 Buick in a dead quarter mile? I liked you better when you weren't saying squat kid." -Buddy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
