kiwix_0.9~beta6-1_amd64.changes REJECTED

Mike Gabriel mike.gabriel at das-netzwerkteam.de
Wed Jun 20 08:19:14 UTC 2012


Hi Vasudev, hi Renaud,

On Di 19 Jun 2012 17:00:25 CEST Vasudev Kamath wrote:

> On 13:10 Tue 19 Jun     , Mike Gabriel wrote:
>> Hi Vasudev
> <snipped>
>> >So do you suggest me to add an override for this? Also 2 more lintian
>> >warnings on call to ldconfig I was never able to resolve it. Do you
>> >know any reason why it is coming
>> >
>> >With Regards
>>
>> I cannot explain that in a precise way, I'm sorry, but I think it's
>> related to installing libzim in a non-shared/private libdir.
>> ldconfig gets launched by debhelper but the library is not in
>> /usr/lib/[<arch>/], so it will not get found.
>>
>> Instead, the /usr/bin/kiwix wrapper script set LD_LIBRARY_PATH to
>> make libzip accessible for the application. (Another option would be
>> setting RPATH in the kiwix-* binaries).
>>
>> Is it possible to tell debhelper not to run ldconfig (which is added
>> to postinst automagically via #DEBHELPER# entry)?
>
> I'm not sure about overriding postinst to not to call ldconfig. But
> just to think of it what if we symlink this libzim library to
> /usr/lib/[<arch>],?

I would leave things as they are before the freeze.

However, it feels that libzim is something rather generic, so to say a  
new library.

So, my question to upstream is: does it make sense to you to split  
libzim and kiwix apart? If so, libzim has to provide versioned library  
.so files. These then can be installed to /usr/lib/<arch> on Debian  
(/usr/lib by make install). This should IMHO the long-run approach.

> Will that be possible? I know we can do it to /usr/lib but not sure
> how to handle <arch> stuff as it differs on different architecture.

In /usr/lib libraries have to be versioned.

> If done, We can see if symlinking makes lintian happy. On the other hand we
> should also check this doesn't break kiwix :-)

Let's wait for upstream, how they react to the suggestion of  
separating libzim from kiwix sources.

Providing libzim as separate upstream tarball would also imply  
separate versioning for both source projects.

Greets,
Mike



-- 

DAS-NETZWERKTEAM
mike gabriel, rothenstein 5, 24214 neudorf-bornstein
fon: +49 (1520) 1976 148

GnuPG Key ID 0xB588399B
mail: mike.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.alioth.debian.org/pipermail/debian-edu-pkg-team/attachments/20120620/e38f3a38/attachment.pgp>


More information about the Debian-edu-pkg-team mailing list