[mapguide-internals] Installation directory structure

[Jason Birch]

If we were going to use a version number, I would prefer to see it at its own level:
 programfiles/OSGeo/MapGuide/2.1/

However, allowing side-by-side installation of major versions is a LOT of work.  For each release, we would have to modify all of the GUIDs within the installer, change all of the port numbers that MapGuide and Apache listen on, change the name of the web virtual directory, and update the documentation.  It also means that we'd have to be pointing to CS-Map through a different mechanism, and if MapGuide is using different versions of PHP we would likely run into problems at the web tier.

All in all, supporting this would take a lot of work, and it would be difficult and time consuming to test interactions with previous versions.  I think it would be more realistic for us to support only a single version and let adventurous folks that want to run side-by-side either compile their own or install on a different computer and copy across.

Jason

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
Sent: March-30-09 8:57 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Installation directory structure

no version number makes side by side installs tricky
and if you look at things like say ms office or autodesk apps
they both use a version number in the sub dir?

anyone know what's best practise these days in ms world?

guess it's different with later versions ?

z

2009/3/31 Jason Birch <Jason.Birch at nanaimo.ca>:
> 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
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>



-- 
Zac Spitzer -
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals