[mapguide-internals] Initial RC1 Build?

Jackie Ng jumpinjackie at gmail.com
Wed Nov 4 04:38:51 EST 2009


Ah I see that I misread your previous post :-)

I'm sure there's a way to do this. The reboot action is governed by two
conditions:

1) The product is not installed

- AND -

2) The CS-Map product feature is not installed

We should be able to slip a 3rd condition in, whose boolean value can be
toggled by a UI prompt. A condition value that evaluates to false, should
avoid the scheduled reboot.

But going back to my original topic, assuming that pre-2.1 installers set a
system environment variable for Proj.4 (I'm sure it did), my original
question still stands. How am I able to install MGOS 2.0.x, 1.2, etc without
needing to reboot?

- Jackie


Crispin_at_1Spatial wrote:
> 
> Jackie,
> 
> As is implied in Kenneth's reply, it is not the reboot that is the problem
> - I can schedule that and cope with the need.  Why reboot?... IISRESET
> picks up most changes - is it the service needing the PATH change for
> CS-Map?  I would have thought this was picked up on the service restart...
> 
> Anyway I digress... the issue with the RC1 installer is that there is no
> warning or option, at the end of the install process the reboot kicks in. 
> You can sneakily leave an edited TXT file open in notepad to force a user
> interface catch but ideally the installer should ask/warn.
> 
> Thanks - Crispin
> 
> 
> 
> Jackie Ng wrote:
>> 
>> I've been thinking about this required reboot, and was wondering...
>> 
>> How did installers pre-2.1 (2.0.x, 1.2, etc) get away without rebooting?
>> Didn't they set a system environment variable as well (for Proj.4)?
>> 
>> - Jackie
>> 
>> 
>> Crispin_at_1Spatial wrote:
>>> 
>>> Hi - just to bring this up before the PSC meeting.
>>> 
>>> I have been using this version (2.1.0.4283-RC1.exe) in our classic .net
>>> / IIS environment for a while now and looks good.
>>> At the last meet there was to be a release before the end of October -
>>> **please** follow the guidelines and launch 2.1 so that the effort can
>>> move on, it's quite painful from this end you know...
>>> 
>>> The only thing is the installer does the rather harsh forced reboot at
>>> the end without warning that on server environments is not ideal.
>>> 
>>>  Crispin
>>> 
>>> 
>>> 
>>> Jason Birch wrote:
>>>> 
>>>> Hi all,
>>>> Well, I got the build done, but did not get to do ANY testing on it;
>>>> ran out
>>>> of time if I want to be functional at work tomorrow.  Have uploaded
>>>> here:
>>>> 
>>>> http://download.osgeo.org/mapguide/testing/
>>>> 
>>>> as: MapGuideOpenSource-2.1.0.4283-RC1.exe
>>>> 
>>>> And the md5sum output is:
>>>> 
>>>> c85fad1a8410988b37099ac307ca8b0f *MapGuideOpenSource-2.1.0.4283-RC1.exe
>>>> 
>>>> Please try installing (on a non-production machine) if you have a few
>>>> minutes, and once we get some hopefully positive notes we can move it
>>>> into
>>>> the release folder for 2.1.0.
>>>> 
>>>> I was hoping to roll FDO 3.4.1 RC1 into this release, but fate was
>>>> unkind :)
>>>>  I did swap the SQLite provider for Traian's back-ported 3.4 version;
>>>> if
>>>> anyone has concerns with this I can put the original version back in,
>>>> but it
>>>> has some nasty bugs.
>>>> 
>>>> Jason
>>>> _______________________________________________
>>>> mapguide-internals mailing list
>>>> mapguide-internals at lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/Initial-RC1-Build-tp3767422p3944027.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.


More information about the mapguide-internals mailing list