<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 17/11/16 16:46, Ben Boeckel wrote:<br>
</div>
<blockquote cite="mid:20161117154614.GA3347@megas.kitware.com"
type="cite">
<pre wrap="">On Thu, Nov 17, 2016 at 10:22:33 +0100, Florian Blachère wrote:
</pre>
<blockquote type="cite">
<pre wrap="">In the binary package of the 5.2.0 release for linux
(ParaView-5.2.0-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz) the python libraries
are under:
'ParaView-5.2.0-Qt4-OpenGL2-MPI-Linux-64bit/lib/python2.7', whereas with
the 5.1.2 release, the files are located under:
'ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/lib/python2.7'.
Is it an intentional change ? Because with this new location, there is
many file conflicts with system python libraries located in
'/usr/lib/python2.7'.
</pre>
</blockquote>
<pre wrap="">
Yes, it was done intentionally, though possibly in ignorance to use
cases where it being separate is a benefit. The idea is to make the
package look as much like you'd expect if ParaView were installed
normally (i.e., a Python module would be put under the expected
site-packages directory).
You can create symlinks from anywhere to the paraview and vtk
directories in the packaged binary and set PYTHONPATH to it if you'd
like to use an external Python as a stopgap, but what is your reason for
wanting an external Python? Would making those packages available to the
packaged Python be sufficient?
--Ben
</pre>
</blockquote>
Ok, I saw the issue <span class="identifier">#16870 after sending
my question. There is also some conflicts with binary files (for
instance mpiexec).<br>
<br>
I think I will drop everything in /opt instead of /usr to avoid
those conflicts with system files.<br>
<br>
Florian<br>
<br>
<br>
<br>
</span>
</body>
</html>