On 01/31/2012 10:48 AM, Roland Grunberg wrote: > As indicated in https://bugs.eclipse.org/bugs/show_bug.cgi?id=367457 > it has been proposed that the Massif plugin from Valgrind switch to > using SWTChart for it's charting/image generation to help downstream > consumers wishing to reduce their dependencies. > > As an example, in Fedora, installing eclipse-valgrind brings in : > eclipse-{dtp,emf,gef}, fop, sac, batik, from its dependency on > eclipse-birt (which provides just the charting functionality). > > SWTChart has been approved for use for the project and is available > in Orbit [1], and the code now sits in the branch feature/valgrind/no-birt. > > What are everyone's thoughts on this proposed change? > > [1] http://download.eclipse.org/tools/orbit/downloads/drops/S20120123151124/ >
Switching to SWTchart sounds like a good plan to reduce the complexity and size of the dependency tree, and I agree with Xavier that it would be a good idea to extend to the other plugins in short order, because if even one plugin still depends on BIRT, we'd now have BIRT *and* SWTchart as dependencies. For our PowerLinux SDK (a free offering from IBM for ppc64 platforms), we will need to go through an internal process to obtain permission to deliver SWTchart as part of the SDK, but since SWTchart is in binary form only inside of the orbit repo, I'm hoping it won't be too difficult. - Corey _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
