<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 07-01-2011 15:07, Jason Roberts wrote:
<blockquote
cite="mid:03b801cbae7c$ab45b0c0$01d11240$@roberts@duke.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">Tamas,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">WIX looks like a great technology for building
the installation package. I’ve never used it but I took a
quick look and it seems to provide what is needed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: rgb(31,
73, 125);">As I understand it, you are pondering whether it
would be better to have GDAL in Program Files\OSGeo\GDAL or
in Program Files\GDAL. Is it simply a question aesthetics or
principle, in which it seems proper to put all OSgeo
projects under Program Files\OSGeo, but there could be
problems coordinating the efforts of multiple projects to
adhere to that carefully and not mash each other’s files? If
that summarizes the issue, then I’d recommend going with the
more practical, less principled approach: put GDAL in
Program Files\GDAL, and OSGeo4W in Program Files\OSGeo4W. It
could get messy if both installers have to be able to create
the Program Files\OSGeo directory but not necessarily delete
it when they are uninstalled, because there could be another
OSGeo project in there.</span></p>
</div>
</blockquote>
<br>
Let me just recall that OSGeo4W proposes the default install
directory as C:\OSGeo4W<br>
This is just my opinion and I feel quite at rest because I'm able to
build GDAL and install it wherever I wont, but I would really hate
that an installer would force me to install in a location contrary
to my will. In particular when that location has blanks in the name
(Program Files).<br>
But, as I said it's just my private view.<br>
<br>
<br>
Joaquim<br>
</body>
</html>