libgig 4.0.0 qsampler 4.2.0 gigedit 1.0.0

[James Cowgill]

Hi,

On 26/11/16 01:44, Jaromír Mikeš wrote:
> 2016-11-25 17:36 GMT+01:00 James Cowgill <jcowgill at debian.org>:
>> OK I've had another look and I think I understand the confusion here:
>> upstream have decided to move the headers from /usr/include to
>> /usr/include/libgig without adjusting anything else to cope with that.
>>
>> Your method would work here, but I think you should ask upstream what
>> they want here since changing it later is a PITA. The options are:
>>
>> All headers in /usr/include, all references to them loose the 'libgig/'
>> prefix.
>>
>> All headers in /usr/include/libgig, all references must have a 'libgig/'
>> prefix (including the headers themselves).
>>
>> All headers in /usr/include/libgig, all references loose the 'libgig/'
>> and -I/usr/include/libgig is added to the pkg-config file.
> 
> Answer somehow came from upstream itself before posting to him ...
> as he reviewed my patch 05-fix-include-dir.patch
> 
>> as far as I remember the previous Debian maintainer of libgig, I think he said
>> the header files should be bundled in a subdirectory according to Debian
>> policies, and the the subdirectory name should reflect the library version
>> (i.e. /usr/include/libgig4/gig.h, etc.). The motivation was to be able to
>> install i.e. two different versions of the same library (i.e. in this case
>> i.e. libgig3-dev, libgig4-dev) which would otherwise cause a file conflict.
>> But obviously I am not up to date regarding latest Debian policies.
> 
> What would be best from debian point of view?
> 
> /usr/include/libgig4/gig.h or /usr/include/libgig7/gig.h
> 
> to reflect rather soname than release?

Usually the header location does not change with the soname / ABI. Most
libraries that do change the header path frequently do it because the
API changes a lot (eg LLVM).

> Or just /usr/include/gig.h and not allow two versions installed together?
> 
> your opinion James?

I think one of the 3 options I gave should be used, but I don't mind
which one. Given that programs seem to be using headers without the
'libgig/' prefix already, the middle options seems the least desirable
but if upstream wants to update all the headers for that option then it can.

As to installing -dev packages together - upstream would also have to
rename the libgig.so symlink as well as installing headers in a
different place. I'm not sure it's worth it.

Thanks,
James

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20161126/bb7aafda/attachment.sig>