Bug#739308: libzip-dev: include file in wrong place

2014-08-07 Thread Thomas Klausner
Hi! Upstream here. I found this bug report. We've put the header file in lib by purpose, because e.g. for multilib installations, /usr/include must be portable over all architectures; so architecture or machine-specific files must be somewhere else. One convention for that is ${PREFIX}/lib/${PRO

Bug#739308: libzip-dev: Include file in wrong place

2014-08-03 Thread John Paul Adrian Glaubitz
On 08/03/2014 12:59 AM, Simon McVittie wrote: > It doesn't force you to think about the include path (in a way, part of > the point of it is to *not* have to think about the include path), but > it does force you to declare which API version you're trying to use > (indirectly, by your choice of .pc

Bug#739308: libzip-dev: Include file in wrong place

2014-08-02 Thread Simon McVittie
On 02/08/14 21:59, John Paul Adrian Glaubitz wrote: > Thanks a lot for the detailed explanation. I was never aware that the > use of pkg-config for the headers was mandatory for GLib and libdbus, > but it actually makes a lot of sense and seems a very clean solution > since it forces you to think a

Bug#739308: libzip-dev: Include file in wrong place

2014-08-02 Thread John Paul Adrian Glaubitz
Hi Simon! Thanks a lot for the detailed explanation. I was never aware that the use of pkg-config for the headers was mandatory for GLib and libdbus, but it actually makes a lot of sense and seems a very clean solution since it forces you to think about the proper inclusion of the header files you

Bug#739308: libzip-dev: Include file in wrong place

2014-08-02 Thread Simon McVittie
On Mon, 12 May 2014 at 02:48:26 +0200, John Paul Adrian Glaubitz wrote: > > /usr/lib/*/libzip/include/zipconf.h looks like multiarch file, > > is it not the right place? > > Indeed. The mentioned header file is platform-specific, so it might > not be wise to put it under the general /usr/include

Bug#739308: libzip-dev: Include file in wrong place

2014-05-11 Thread John Paul Adrian Glaubitz
> /usr/lib/*/libzip/include/zipconf.h looks like multiarch file, > is it not the right place? Indeed. The mentioned header file is platform-specific, so it might not be wise to put it under the general /usr/include directory structure. On the other hand, the libzip-dev package is not a Multi-Arc

Bug#739308: libzip-dev: Include file in wrong place

2014-03-08 Thread Mateusz Łukasik
control: +patch I made bugfix patch and also attach NMU debdiff. Description: Fix including headers file in wrong place Author: Mateusz Łukasik Bug-Debian: http://bugs.debian.org/739308 --- b/lib/Makefile.am +++ b/lib/Makefile.am @@ -3,7 +3,7 @@ libincludedir = ${libdir}/@PACKAGE@/incl lib_

Bug#739308: libzip-dev: Include file in wrong place

2014-02-17 Thread Christian Marillat
Package: libzip-dev Version: 0.11.2-1 Severity: serious Dear Maintainer, zipconf.h is in /usr/lib/i386-linux-gnu/libzip/include/ when the rigth place is (was the case in previous package 0.10.1-1.2) /usr/include Christian -- System Information: Debian Release: jessie/sid APT prefers unstabl