Re: Question about packaging projectchrono and duplicated source code
On 02/05/17 08:21, Andreas Tille wrote:
> Hi,
>
> On Mon, May 01, 2017 at 08:10:29PM +0200, Anton Gladky wrote:
>> if it is really so, that the code forked, removed, edited, feel free
>> to let this embedded code be in the source of chronoengine. Please
>> do not forget to make a note in d/copyright.
>
> Depending from the number of changes it might be worth considering to
> provide the changes as patches against the upstream code and point
> upstream to these. (I have not checked whether this method is feasible
> in this actual case.)
>
Andreas,
that kind of code could be complicated. If Damien is correct, the number of
hours to make it doesn't justify the job. I propose to keep them as a fork, and
in parallel try to contact both upstream to merge changes.
Damien, could you create the git repo for projectchrono in alioth and work there?
Best regards,
Leopold
>>
>> 2017-05-01 18:41 GMT+02:00 dada <dada@yakuru.fr>:
>>> Hello all,
>>> Following the discussion here [1], I am trying to package
>>> the projectchrono C++ library [2] for debian.
>>>
>>> The main problem is that the projectchrono embeds some sources [3]
>>> from the bullet library [4] that is already packaged by Debian [5]...
>>> and debian policy forbids code duplication...
>>>
>>> Strictly speaking, the bullet codes embedded inside projectchrono
>>> is not the same as the bullet "main stream" one. Some parts
>>> were edited/removed/added, etc... and it's look like a fork.
>>>
>>> I don't know how to solve this problem.
>>>
>>> 1- A first solution consists in removing all the bullet
>>> part of the projectchrono. By the way, some features given
>>> by the own bullet version of projectchrono will be loose.
>>>
>>> 2- A second solution is to keep the source code and to consider
>>> it as a fork and not as a duplicated one.
>>>
>>> Tell me if you have an idea on the right way to solve this problem.
>>> Best regards, Damien.
>>>
>>>
>>> [1] https://lists.debian.org/debian-science/2017/04/msg00069.html
>>> [2] https://projectchrono.org/
>>> [3]
>>> https://github.com/projectchrono/chrono/tree/develop/src/chrono/collision/bullet
>>> [4] http://bulletphysics.org/wordpress/
>>> [5] https://packages.debian.org/source/sid/bullet
>>>
>>
>>
>
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Reply to: