Hey Michael Biebl, I guess that people don't know that they need a file called liblibrary-version.pc, is what might be the real thing we learned here (if anything). Unfortunately, because we devs are morons that can't agree on anything, it could also be library.pc, library-version.pc, libimaherowhocameupwithsomethingstupidiinventedmyself.pc and etc.pc .. I wonder what we could do about this. Surely if Debian leads on a solution (does something, and makes it a norm), the rest of the inferior distributions will eventually (after ten years of showing that they know it better than forming an agreement) acknowledge that it just doesn't matter and go for what (after those ten years) is a Belgian-like incredibly stupid compromise. To then fall back to Debian's standard of twenty years ago, another ten years later. The truth is that de-facto standard distributions like Debian and its packaging creates some peace and standardization. So again, I wonder what we could do about this. Kind regards, Philip On Tue, 2017-03-21 at 03:51 +0100, Michael Biebl wrote:
2017-03-21 3:25 GMT+01:00 Chris <cpollock embarqmail com>:Thanks Michael, that took care of all except the glib >=2.44.0 issue which I'll have to work on. These have now popped up which I also need to work on configure: error: Package requirements (glib-2.0 >= 2.44.0 libsoup-2.4 >= 2.40 libxml-2.0 >= 2.6 json-glib-1.0 >= 1.0) were not met: No package 'libsoup-2.4' foundlibsoup-2.4 is missing $ apt-file search libsoup-2.4.pc libsoup2.4-dev: /usr/lib/x86_64-linux-gnu/pkgconfig/libsoup-2.4.pc
Attachment:
signature.asc
Description: This is a digitally signed message part