[mapguide-internals] Installation directory structure

[Jason Birch]

Quick note:  Agreed, but would prefer "MapGuide", without version number in path.  And really, really, want to see data dir locations (logs, repos, packages, temp) remain configurable at install time.

Jason

----- Original Message -----
From: mapguide-internals-bounces at lists.osgeo.org <mapguide-internals-bounces at lists.osgeo.org>
To: mapguide-internals at lists.osgeo.org <mapguide-internals at lists.osgeo.org>
Sent: Mon Mar 30 19:21:38 2009
Subject: [mapguide-internals] Installation directory structure


Hi All,

There seems to be some talk that the current directory structure used by the installer is not quite ideal. If so, then what should the ideal structure be?

I would prefer something like:

$INSTALLDIR = C:\Program Files\OSGeo\MapGuideOpenSource

$INSTALLDIR\Server
$INSTALLDIR\WebServerExtensions
$INSTALLDIR\CSMap

This would be like the structure of previous releases, except by default it goes under the 'OSGeo' name and it will work-around the fusion having hard-coded the web server extension path. Jason suggested locking down the Server and Webextension directories which I think is a good idea. The less number of configurable paths, the better.

Thoughts?

- Jackie

P.S. I didn't come up with the initial directory structure. I just went with the flow :-)
-- 
View this message in context: http://n2.nabble.com/Installation-directory-structure-tp2560810p2560810.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals