Open CASCADE Technology 6.7.0 was released on December 18, 2013. Here are the release notes: http://www.opencascade.org/about/news/issue199/
Created attachment 367780 [details] opencascade-6.7.0.ebuild
Created attachment 367782 [details, diff] opencascade-6.7.0-fixed-DESTDIR.patch
Created attachment 367824 [details] opencascade-6.7.0.ebuild updated the ebuild correcting a bad patch name and removing the redefinition of ${S}
I have successfully tested the compilation on my amd64 system. I'm wondering if it makes sense to slot the package, if compiled with debug symbols it needs more than 800MB of space for each slot.
OCC slotting is IMO good idea, as it's not compatible between releases. Also, there is community edition
In portage there are just a bunch of packages depending on opencascade. Would it make sense to have concurrently installed so many versions of opencascade? I agree on the possibility to have installed at the same time OCC and the community version. OCC's ABI often changes, I guess that the EAPI-5 slot operator mechanism is enough to trigger the rebuilding of packages using the library.
(In reply to Fabio Rossi from comment #6) > ... I guess that the > EAPI-5 slot operator mechanism is enough to trigger the rebuilding of > packages using the library. That's right. I just want to provide a way to preserve the relatively expensive compile output of opencascade and consecutive rebuilds. If I bump opencascade and freecad (w/ or w/o slot operator rebuild) won't recompile I'm doomed. Slots are not intended to waste space, but to provide alternatives. After a clean update, emerge -a --depclean should drop the older slots (just like it does at gcc et al).
+*opencascade-6.7.0 (23 Apr 2014) + + 23 Apr 2014; Michael Weber <xmw@gentoo.org> + +files/opencascade-6.7.0-fixed-DESTDIR.patch, +opencascade-6.7.0.ebuild: + Version bump thanks to Sławek Lis and Fabio Rossi (bug 496968). +
