[CCC DEV] Prep for OSCON

[cljacobsen at gmail.com]

Nope, we have not looked at anything but Innosetup since we started
the project. I chose Innosetup in the past due to its "lovely coding
experience with elements of"*... Pascal. nsis does not appeal to me in
that lovely coding experience respect :)

The other obvious option is Windows Installer (MSI), but since I don't
know much about it perhaps it is not so obvious after all.

Given timeframes and things I will probably continue with Innosetup
unless somebody either:
1) takes over handling the installer
2) provides some very compelling arguments for using something else

I'd prefer option 1!

Cheers,
  Christian

* to steal the expression which nsis uses to describe its 'coding
experience', except for the language. Personally I detest PHP (with
indifference) and abhor all assembly other than MIPS or Transputer.

On 28 June 2010 12:13, Martin Ellis <ellism88 at gmail.com> wrote:
> Have you looked at http://nsis.sourceforge.net/Main_Page as a installer?
>
> On Mon, Jun 28, 2010 at 10:49 AM, cljacobsen at gmail.com
> <cljacobsen at gmail.com> wrote:
>> Hi Dave,
>>
>> I have been working on the Windows installer (though not a great deal
>> for the past few months). Currently it is possible to build all the
>> binaries for Windows. This works by following the instructions in
>> trac: [1]. I have not tried that build for a while so changes in the
>> sourcecode in trunk may or may not have broken stuff. What is still
>> missing is an update to occPlug to make it work in Windows (ie, run
>> the correct commands in the right way from the appropriate paths) and
>> building an installer and/or zip file with everything nicely packaged.
>> I did some work in the direction, but I don't think I committed it.
>>
>> So in terms of things that need doing, here are some things:
>>  * check that trunk still builds using instructions from [1]
>>  * I need to commit some windows related occPlug
>>  * Figure out a layout for the distribution
>>  * Make a zip only package
>>  * Figure out what framework we are going to use for installer
>>    * We have used innosetup in the past [2]
>>  * Figure out integration with winsparkle [3]
>>
>> So if you want work on the windows stuff I'd suggest that you check to
>> see if things still build and we can then coordinate from there.
>>
>> Cheers,
>>  Christian
>>
>> [1] http://projects.cs.kent.ac.uk/projects/kroc/trac/wiki/WindowsDistribution
>> [2] http://www.jrsoftware.org/isinfo.php
>> [3] http://winsparkle.org/
>>
>> On 26 June 2010 18:49, Dave Gilmore <gilmorenator at gmail.com> wrote:
>>> ---------- Forwarded message ----------
>>> From: "Dave Gilmore" <gilmorenator at gmail.com>
>>> Date: 26 Jun 2010 17:48
>>> Subject: Re: [CCC DEV] Prep for OSCON
>>> To: "Matt Jadud" <jadudm at gmail.com>
>>>
>>> Matt,
>>>
>>> Do you already have someone working in the Windows installer?
>>>
>>> Cheers,
>>>
>>> Dave.
>>>
>>>>
>>>> On 26 Jun 2010 16:11, "Matt Jadud" <jadudm at gmail.com> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Out of curiousity:...
>>>
>>> _______________________________________________
>>> developers mailing list
>>> developers at concurrency.cc
>>> http://unhosting.org/mailman/listinfo/developers
>>>
>>>
>>
>> _______________________________________________
>> developers mailing list
>> developers at concurrency.cc
>> http://unhosting.org/mailman/listinfo/developers
>>
>