Hi Mathieu, > Did you either: > - understood why cgal had to patch core++
There was a time when CGAL used the CORE library as external package. But at some time around the 1.7 release the development of CORE was very slow (and probably still is). I.e., the code did not compile with current gcc versions; there were knowns bugs with patches provided, but no bugfix releases; different (pre-)releases with the same version number. In short, using an external CORE package as released from upstream caused too many problems and it was decided to switch to an internal copy of the sources. > - check what were the differences There were quite some changes and I did not check them all. Some of the changes are bug fixes, and in parts exist as patches in the core++ package. Some of the changes made the code compile with recent gcc and can be -in this or a different form- found in the core++ package as a patch. I bet there are also changes which are not present in the core++ package. Part of the problem is to identify the exact CORE version that was included in the CGAL sources. Unfortunately, the CORE project made several (pre-)releases without changing the version number :-( > - is upstream willing to use a newer core++ dist if this match with > dev. of core++ I haven't noticed such plans on the mailing list. CORE is not a strict dependency of the CGAL library. CGAL can be used without CORE, but looses some parts of its functionality then. From time to time there are vague ideas to drop CORE support completely. Joachim -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
