Hello, there is a file collision with sci-libs/vtk-5.4.2: >>> Installing (1 of 1) sci-visualization/paraview-3.6.1 * Detected file collision(s): * * /usr/bin/lproj * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sci-libs/vtk-5.4.2 * /usr/bin/lproj Reproducible: Always Steps to Reproduce:
Hi Oliver, Thanks for the note and I kind of suspected this was the case. It seems paraview and vtk just don't get along all that well (see also your bug #212947) likely because paraview ships most of vtk itself. Even though I don't like this solution, for the time being I've made vtk a blocker in the paraview ebuild. Maybe there's a way we can get around this eventually. The best solution would of course be that paraview used the installed version of vtk instead of building its own, but this had to be done upstream. Best, Markus
(In reply to comment #1) > Even though I don't like this solution, for the time > being I've made vtk a blocker in the paraview ebuild. > Maybe there's a way we can get around this eventually. > The best solution would of course be that paraview > used the installed version of vtk instead of building > its own, but this had to be done upstream. Hello Markus, thanks for the quick reply. Instead of blocking vtk and paraview each other, can we just delete the /usr/bin/lproj from the paraview ebuild? I don't even know what this executable does. Thanks, Oliver
Maybe we could, but I need to find some time to investigate. If this is the only file clash then this might be a solution. How about those issues you reported in #212947? If they are still relevant then having them install side by side might be more complicated. cheers, Markus
*** Bug 279293 has been marked as a duplicate of this bug. ***
> If this is the only file clash then this might be a solution. Yes this seems to be the only file clash. > How about those issues you reported in #212947? These are gone with newer versions. And at the moment I'm using vtk and paraview side by side, so I would like to have both installed at one machine. Because the vtk version, which is bundled within paraview doesn't have the readers from vanilla vtk I need. Thanks, Oliver
Ok, let me have a look then. Since I honestly don't know what lproj does, maybe a better strategy would be to simply rename lproj to lproj_paraview so we can keep it around? thanks, Markus
(In reply to comment #6) > Ok, let me have a look then. Since I honestly > don't know what lproj does, maybe a better > strategy would be to simply rename lproj to > lproj_paraview so we can keep it around? > > thanks, > Markus > It seams that rename lproj of paraview just works. I have removed the lproj of paraview to paraview-lproj and paraview works well in my situation (I use paraview to visualize 3d dataset in vtk format.).
(In reply to comment #6) > Ok, let me have a look then. Since I honestly > don't know what lproj does, maybe a better > strategy would be to simply rename lproj to > lproj_paraview so we can keep it around? > I think this is a very good idea from my side of view. Thanks, Oliver
Sounds like a plan - I'll give this some testing today and if all looks well I'll push this out as paraview-3.6.1-r1. Thanks, Markus
paraview-3.6.1-r1 is now in portage and should play well together with vtk (at least it does for me). Thanks to all for your help. cheers, Markus
