<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>I have two concerns with ParaView builds for release – figuring out what version of ParaView we are building, and where we get the dependent packages. </div>
<div> </div>
<div>Here at Sandia, we have an issue whenever ParaView tries to pull any source code from the internet. This occurs for the following reasons.</div>
<ul style="margin:0;padding-left:36pt;">
<li>ParaView itself has two scenarios:</li></ul>
<ul style="margin:0;padding-left:72pt;">
<li>We have some systems that can see the internet, and some that cannot. These two have to connect together as client/server. Thus, both have to be built from the same source code, with the same version numbers, and one can’t think it is a specific git version
and the other be blind. Both have to think they are just some version number of ParaView.</li><li>We are running on a platform (client and server) that cannot see the internet, and may not even have connectivity to the rest of our network. ParaView client and server still needs to build, with me (or the CMakeLists.txt, etc) telling it what version
it is building.</li></ul>
<ul style="margin:0;padding-left:36pt;">
<li>For other “stuff”, such as Mesa, Python, Qt, etc, we need the option to not have the build look at, and pull, copies of these datasets. Once again, the usecase is where we are building for a system that is not connected to the internet – or any other
part of the network. This must work standalone.</li></ul>
<div> </div>
<div>If I were king, we would do the following with ParaView:</div>
<ul style="margin:0;padding-left:36pt;">
<li>Allow me to tell ParaView what version we are building – turning off looking at Kitware for the Git version.</li><li>On dependent packages:</li></ul>
<ul style="margin:0;padding-left:72pt;">
<li>If the package exists, use it. Don’t look at the internet.</li><li>If the package doesn’t exist, try to find it from the system. MPI will often happen this way.</li><li>If the package isn’t on the system, go get it.</li></ul>
<ul style="margin:0;padding-left:36pt;">
<li>On the superbuild, Kitware would make sure that ParaView built from scratch on a client – and server – setup that was disconnected from the internet.</li></ul>
<div style="padding-left:36pt;"> </div>
<div>For some reason, I am thinking that Utkarsh convinced me that our current .paraview.version flag isn’t working, but I cannot for the life of me remember why. Also, for all I know, we are going this direction. I just didn’t want to be surprised and wish
I had spoken up.</div>
<div> </div>
<div>There is my $0.02. </div>
<div> </div>
<div>Alan</div>
<div> </div>
<div><font size="2"><span style="font-size:10pt;">--------------------------------------------------------</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">W. Alan Scott</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">ParaView Support Manager</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;"> </span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">GAITS</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Sandia National Laboratories, MS 0822</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">Org 9326 - Building 880 A1-C</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">(505) 284-0932 FAX (505) 284-5619</span></font></div>
<div><font face="Arial" size="2"><span style="font-size:10pt;">---------------------------------------------------------</span></font></div>
<div> </div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>