Re: About openmeca package

[Anton Gladky <gladk@debian.org>]

Looks fine! Yea, sometimes packaging for Debian requires
the removal of some embedded code and replacing it by
external dependencies. But it increases the quality of the
package and reduces its size..

Best regards

PS If you need sponsorship of the package, I will probably be
able to review it during SunCamp 2017.

Anton


2017-04-26 22:53 GMT+02:00 dada <dada@yakuru.fr>:
> Hello Anton, Hello Leopold,
> Thank you for your help. I miss the debian policy about embedded copy of
> codes.
> It's clear that my package does not respect this rule.
>
> Following this discussion, here is the plan :
>
> 1- push out boost from the openmeca package. It's technically easy.
> Therefore, if users notify some bugs about backward compatibility, I will
> fix this issue as upstream author.
>
> 2- push out chronoengine library from openmeca and package chronoengine for
> debian. I plan to package
> only the C++ core module of chronoengine to minimize technical and copyright
> problems.
> As Leopold said, It induces to push out some part of the chronoengine code
> that embeds
> itself some source codes already packaged by debian (the bullet library
> [1]).
>
> What do you think about this plan ?
> The second part will be hard for me, I will probably need some help from the
> debian community.
>
> [1]: http://bulletphysics.org/wordpress/