[Debian-med-packaging] FW4SPL package

Flavien Bridault fbridault at ircad.fr
Mon Nov 28 09:57:03 UTC 2016


Le 25/11/2016 à 17:38, Flavien Bridault a écrit :
> Le 25/11/2016 à 17:35, Andreas Tille a écrit :
>> Hi Flavien
>>
>> On Fri, Nov 25, 2016 at 05:18:38PM +0100, Flavien Bridault wrote:
>>> Ok thanks for that change , I was not sure whether or not to use this
>>> flag. That's good to know.
>>
>> :-)
>>  
>>> For fw4spl, you might want to test it in the current state. I tried to
>>> migrate to use d-shlibmove as well but it fails:
>>>
>>> make[2]: Leaving directory '/home/flav/dev/fw4spl/obj-x86_64-linux-gnu'
>>> d-shlibmove \
>>>         --commit --multiarch --exclude-a --exclude-la \
>>>         debian/fw4spl/usr/lib/*.so
>>> Library package automatic movement utility
>>> /usr/bin/d-shlibmove: expected [debian/fw4spl/usr/lib/*.so] to be a
>>> symlink, but it is not
>>> debian/rules:20: recipe for target 'override_dh_auto_install' failed
>>> make[1]: *** [override_dh_auto_install] Error 1
>>>
>>> I guess this is simply because I don't have such filenames :
>>>
>>> libfwMemory.so.0
>>> libfwMemory.so.0.1
>>>
>>> so I probably miss a libfwMemory.so as well to be compliant with the
>>> expected naming layout. Probably the best option is to patch the
>>> CMakeLists.txt to produce the correct output instead of trying to fix
>>> this in a install or post-install step.
>>
>> Yes, that's probably the solution and I think I do not burn compting
>> power to verify this.  Please keep me informed if you have patched
>> CMakeLists.txt (I'm quite weak with cmake, soory).
>>  
> 
> Yeah no problem, that's our job to sort this out. This would be probably
> a good fix to push then to upstream. That's also the kind of things I
> like in packaging to Debian, is that it forces us to install and pack
> things in a standard and better way. :)
> 
> I'll keep you informed, probably nothing new before monday, though.

Okay the symlink problem was easily fixed with CMake.

But now I am a bit confused about the install process. I don't feel yet
comfortable at all with all the possibilities, like all the different
targets (override_dh_install override_dh_auto_install
override_dh_install-arch, etc...) and what exactly does d-shlibmove. I
don't manage to find a good documentation for this tool. Currently I try
to compare with other packages.

Well the problem is, if I try to use d-shlibmove, the utility returns
several errors :

PKGSHL=libfwcore0
E: line [Provides:.*libfwcore-dev] not found in debian/control section
for libfwcore0-dev
E: line [Conflicts:.*libfwcore-dev] not found in debian/control section
for libfwcore0-dev
E: line [Section: libs] not found in debian/control section for libfwcore0
E: line [Section: \(devel\|libdevel\)] not found in debian/control
section for libfwcore0-dev
E: line [Depends:.*libfwcore0] not found in debian/control section for
libfwcore0-dev
E: line [Depends:.*[$]{shlibs:Depends}] not found in debian/control
section for libfwcore0
Error occurred, aborting
debian/rules:20: recipe for target 'override_dh_auto_install' failed

So first I understand a package will be created for each library. That's
definitely not what I want. For now, we used to create a simple fw4spl
package with everything inside.
Second it tries to create a -dev package. Again, that's not what I want,
at least for now. We plan to create proper -dev packages in a near
future. But for now I would rather focus on getting the previous package
working like it was, unless you don't agree of course.

So could you give me some guidelines on this ? Should I really use
d-shlibmove with this goal in mind ? Should I play with the --override
or --extralib flags ? Or should I stick with *.install files and change
what is necessary to get multiarch support (that was the initial goal) ?

Thanks again for your help. :)

> 
>> Kind regards
>>
>>       Andreas.
>>
> 
> 
> 
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20161128/0690f81e/attachment.sig>


More information about the Debian-med-packaging mailing list