<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Comic Sans MS";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>gentle para-people,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>thanks to berk is found what was killing a
recent (last week and today’s) cvs paraview build to die<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>right out of the gate on my WinXP machine.
it was the lookmark stuff.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=3 face="Comic Sans MS"><span
style='font-size:12.0pt;font-family:"Comic Sans MS"'>see </span></font><font
face="Courier New"><span style='font-family:"Courier New"'><a
href="http://public.kitware.com/pipermail/paraview/2005-July/001757.html">http://public.kitware.com/pipermail/paraview/2005-July/001757.html</a><o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=3 face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>this is still a problem for me (and perhaps
other para-heads -- with apologies to jimmy buffet fans)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>the reason seems to be a collision between
our security policy and the assumptions the lookmark<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>developers have made. I can build and
use today’s cvs just fine at home where I have admin priviledges;<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>and our draconian security policies aren’t
strictly adhered to;<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>but the security policy at work does not
allow me ( a generic, non-admin user) to write files on say c:\<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>I tracked down the offending stuff and
exorcised it so paraview will fire up and run;<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>but that sucks (because I’m lazy) and
I will have to do this every time I checkout<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>a new cvs version. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>perhaps the developers could put a chunk of
code that checks for some environment variable<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>PARAVIEW_LOOKMARKS and if it’s
present do stuff there; if it’s not do what it current does.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Comic Sans MS"><span style='font-size:
12.0pt;font-family:"Comic Sans MS"'>-m<o:p></o:p></span></font></p>
</div>
</body>
</html>