[mapguide-internals] MapGuide Open Source 2.1 -whereisthecontinuous integration system ????

[Jason Birch]

That sounds cool Haris, Davor!

The project that I created was _very_ minimal, but I can definitely see
a way forward.  By combining a modified version of Paraffin (used to
keep the component/file lists up to date) with regular WiX builds, we
should have a way forward to creating nightly or weekly installers.

Modifications that will be required to Paraffin:

- Need to be able to not output the initial Directory tag so that files
can be installed to a different directory name than they are stored in.

- Needs to be updated to use schema header, and to write long file names
to the Name attribute and not write the LongName attribute to account
for changes in 3.0

- Needs to make a few of the file attributes optional

A couple things I was thinking of as I was hacking away:  Things like
the package name, version, package GUID, etc should be pulled out of the
config file into variables.  This will allow us to tag the nightly
installers properly, and do things like use the same config for both x86
and x64 installers.   Also, we should make sure to take advantage of
WiX's localization support, even if we only provide en-US strings
initially.

I wonder if we need to continue distributing Apache and PHP with
MapGuide.  Can we just integrate with pre-installed versions?  WiX
allows fairly strong INI file modification capabilities, so it shouldn't
be a problem modifying existing PHP.ini files.  For Apache, I would like
to see MapGuide's configuration done in an "include" file so that it
could be added to any vhost (assuming that this is possible).

IIS installation is likely going to be a bit of a challenge.  WiX
includes an extension for IIS, but it's not all that well documented.

Some of the challenges that I would like to see us deal with once
everything else is working properly:

- Allow the user to select alternate locations for components like the
Repositories folder, etc

- Allow the user to choose which IIS Website to install the virtual
directories to

- Allow the user to set the MapGuide Administrator, Author passwords

- Allow the user to choose which FDO providers are initially enabled

Jason

-----Original Message-----
From: Haris Kurtagic
Subject: RE: [mapguide-internals] MapGuide Open Source 2.1
-whereisthecontinuous integration system ????

I believe that we in  SL-King ( Davor Klemen) could put time to help to
create and manage windows installations.

WiX looks like nice way to go.
Jason, Davor will look into projects you already did and try to get
familiar with MG/WiX.
If you already have ideas/tasks for further steps, we are all ears :)