I won't speak for Stephane, but I think that such an option would be 
helpful.

In particular, it would facilitate multiple versions of Csound on the same 
computer.

Art Hunkins

----- Original Message ----- 
From: "Michael Gogins" 
To: 
Sent: Tuesday, September 23, 2008 3:35 PM
Subject: [Csnd] Re: Re: Re: Re: Version 5.09 released


It could also be an option in the installer to set, or not, these 
environment variables. Would that solve your problem?

Regards,
Mike

-----Original Message-----
>From: Stéphane Rollandin 
>Sent: Sep 23, 2008 2:50 PM
>To: csound@lists.bath.ac.uk
>Subject: [Csnd] Re: Re: Re: Version 5.09 released
>
>> Wouldn't you get the same installation by using the installer,
>> specifying "no Python", then deleting the environment variables (which
>> amount to 6 or so entries)?
>
>yes, indeed.
>
>> I'd be interested in knowing what, if any, *other* value there would be
>> in offering a .zip archive version. (One idea would be to offer a
>> further "stripped-down" version. I work in such a version myself -
>> putting everything [which is not much] in a single folder. But this is a
>> customization for my own unique purpose.
>
>I use a stripped-down version myself, but it's quite likely that no two
>people would agree about what should be in it.
>
>now, to answer your question: I develop a set of programs where csound
>is mainly a component. currently, I have to launch the installer in a
>virtual OS (a sandbox so that I know for sure my system settings will
>not be messed up), pick up the files, maybe kill a couple python-related
>dlls, then add a csound.bat allowing me to work with csound without the
>need for any environment variable (see below).
>
>then I can go back to my main system, where I can at last work at the
>same time with different flavors of csound, in a space not polluted by
>global environment variables, and thus develop and test my software as I
>wish.
>
>so a plain zip would be nice for me. I would just have to unzip it,
>period. no need for any *other* value :)
>
>it would be even more useful to an end-user of my software: he could
>upgrade csound by himself, simply by replacing the content of a folder.
>currently, it is a very non-trivial operation that I do not even want to
>describe in a how-to text.
>
>does this answer your question ?
>
>>
>> If there is a verifiable need for a .zip distribution, and the above
>> assumptions are correct, it should be simple for someone to install the
>> float version (default location), without Python, zip it up (optionally
>> stripping it down a bit - any stripping would need to be discussed), and
>> send it back somewhere for download.
>>
>> I'd volunteer for such a task, always upgrading to the most recent
>> *float* release (Windows - I only use the real-time version). I could
>> upload to my own website, to csounds.com or to sourceforge, for that
>> matter.
>
>the point is: I don't understand why the csound maintainers do not
>provide the .zip on sourceforge along with the installer; for them, it
>should be an utterly trivial task. considering that I and others have
>asked for this at least a dozen times these last *years*, the fact that
>  this is not there yet just puzzles me.
>
>... as do the python dependency, but that is another story.
>
>
>regards,
>
>Stef
>
>
>appendix: the csound.bat contents
>
> @cd %~p0
> @set CSOUNDRC=..\.csoundrc
> @set OPCODEDIR64=..\plugins64
> @set OPCODEDIR=..\plugins
> @set RAWWAVE_PATH=..\samples
> @set SFOUTYP=WAV
> @set PYTHONPATH=%PYTHONPATH%;%~p0
> csound.exe %*
>
>... just put this in the csound/bin folder, zip the csound folder and
>you're done.
>
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>csound"





Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
csound"=