Examine csound-build.tex, and you will see what it takes to put this installer together. It can't be scripted because not everything works, some steps have to be done twice, and so on. So manual checks have to be done at various steps in the process. Oh yes, and what works and what does not work keeps changing.

Replacing the installer altogether with a zip file is in fact an appealing option, but then newbies would not get a Start Menu with csound5gui and the manuals on it. The whole purpose of the installer is to enable a no-brains startup.

Regards,
Mike

-----Original Message-----
>From: Stéphane Rollandin 
>Sent: Sep 24, 2008 4:28 AM
>To: csound@lists.bath.ac.uk
>Subject: [Csnd] Re: Re: Re: Re: Re: Version 5.09 released
>
>Michael Gogins a écrit :
>> It could also be an option in the installer to set, or not, these environment variables. Would that solve your problem?
>
>I would not launch an installer in my main system unless I'me 100% sure 
>  it will not mess up with my settings, so to me such an option would 
>not change anything. but it could be useful to others.
>
>I don't want to be dense, but here is the question I would like an 
>answer to: why not provide a plain extra zip distribution along with the 
>installer ? why is that a problem for you ? shouldn't it be as simple as 
>launching one more script in your packaging process ? I don't understand.
>
>
>best regards,
>
>Stef
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

> One thing to note is that I don't think this is an either-or option,
> and that Stephane may be implying the same, that we might have two
> distributables, one the installer and the second one a zip. 

of course: I never asked for a zip *instead* of an installer.

Stef