[mapguide-internals] Re: 32 bit installer on build machine

[UV]

Sorry but I dont agree.
A full build cycle SHOULD include a installer. thats a pretty standard 
way of developing code these days....
Furthermore, as you explained correctly installing manually is a hassle!!!

You are right that should happen on a build server! 
but my build server because your build machine does not build my 
features i want to test, so I need the installer....
in particular when deploying the testbuild to a different server for 
load testing ....

So why should I not use the installer???
I couldnt use it so far because it hasnt been made useful without any 
documentation!
(thats the comment I made)

I dont know of any valid reason for omitting documentation for any 
public code!
Documentation does not reallly belong in this mailing list but in the 
repository.
Sorry, but i think comitting so much code to the Installer branch 
without providing a README is simply an incomplete submission.

Its a pity how many developers still think working code is the only 
relevant outcome of their job, I mean this is Open Source isnt it?

Trevor Wekel wrote:
> Hey UV,
>
> Developers shouldn't have to create installers.  It's too much of a hassle.  That's why we have a build machine.  And I also thought about doing a manual install myself... for about 30 seconds... Then I pinged Jackie on -internals.
>
> Manual install is a hassle to do on Windows.  Click here, click there, virtual directory this, application that, still doesn't work.  Oops picked the wrong version of .Net.  Yuk.  Been there...  Done that... The installer does it better.
>
> http://download.osgeo.org/mapguide/testing/MapGuideOpenSource-2.2.0.4686-Test.exe
>
> Or if you really, really, really want to build an installer yourself
>
> http://svn.osgeo.org/mapguide/trunk/Installer/scripts/
> http://svn.osgeo.org/mapguide/trunk/Installer/scripts/buildmgx86.bat
>
> The batch files are specific to the build machine and there are additional software packages needed to support the build and installation process (Java SDK, ant, doxygen, Wix, Paraffin).  It took a couple of days to set up.  Eventually the batch file will get rolled into an automated build process.  But it works for now.
>
> Regards,
> Trevor
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of UV
> Sent: March 23, 2010 8:58 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] Re: 32 bit installer on build machine
>
> Why is there no README file in the Installer top level directory with 
> this information?
> I could never find any info on how to get it to work so I gave up using 
> this and had to install manually!
>
> Documentation is essential! Whats the point of writing code nobody else 
> can use?
>
>
> Jackie Ng wrote:
>   
>> Hi Trevor,
>>
>> The build.bat has an -a=generate option that rebuilds the wxs files from
>> scratch. The installer uses MgDev\Release as the default directory from
>> where Paraffin will generate its file list.
>>
>> Because the MG output directory does not initially have the Apache, PHP and
>> Tomcat binaries, these need to be copied over. The -a=prepare option
>> fulfills this purpose.
>>
>> I usually have paraffin.exe inside the Installer root directory.
>>
>> After a successful run of MgDev\build.bat w/ default settings, I do the
>> following from the Installer directory:
>>
>> build.bat -a=prepare
>> build.bat -a=generate
>> build.bat
>>
>> - Jackie
>>   
>>     
>
> _______________________________________________
> 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
>