Hello Leopold, Thank you for your answer !I am agree with you... therefore I want to explain why I made this "bad choice".
I have a long experience with the Boost serialization lib and I experienced A LOT of troubles due to the non-backward compatibility of this library. The results is that users can't share freely their files between them. I was tired to manage this problem, so I decide to keep a frozen version
of boost serialization inside openmeca.If the current version of the boost serialization fix this problem... No problem ! I will enjoy to keep this lib outside of openmeca. But it will be not possible to guarantee the backward compatibility between openmeca version that uses different version of the boost serialization lib.
Now let's talk about ChronoEngine. OpenMeca is a old project and I use one of the first free version of ChronoEngine (in 2013). At that time, the compilation was managed by MS-Visual-Studio project and it was a nightmare to compile it under GNU/Linux and I promise me to never do it again :), When I read your mail, I break my promise and I try again. Now, chronoengine use CMake and apparently, the compilation is quiet simple.... but I suspect that the full compilation (with all chronoengine features) will not be trivial.
To be honest, I spent a lot of time in trying to debianize openmeca.I will try to do something with chronoengine but, depending on the complexity of this task,
I am not sure that I have the time to do that. Best regards, Damien. Le 2017-04-26 08:48, Leopold Palomo-Avellaneda a écrit :
Hi, I have read a bit about the openmeca package. I'm sorry, but IMHO the package is not well done from the beginning. Let me explain my opinion because I would not be destructive. openmeca source has three folders: * ChronoEngine * OpenMeca * Serialization Your package should be just OpenMeca. Why?* ChronoEngine should be a single package. It's a project, AFAIK you are notupstream (PROJECTCHRONO , https://github.com/projectchrono/chrono). This project deserves a single package. I think that it wouldn't be easy. It use several code from bullet (gimpact, and should be dropped)* Serialization. It's Boost and we have it in Debian. I think that you cannot put this code because it violates some policy to repeat it. And, looking thesources, in a fist quick look, they are almost equal than my boost serialization folder from Jessie. So, my recommendation:- To package ChronoEngine, patching the needed code to use the standardinstallation of bullet. Work with upstream about it. I think that they will be open.- Drop from your code all the Serialization folder and use the standardinstallation of Boost - Package "just" Openmeca. Best regards, Leopold